AI ERP with agents inside the systems you run
AI phone and voice agents for real calls
LLM.coPrivate, self-hosted LLM deployments
Legal AI infrastructure for firms
AI RFP discovery and response drafting
Automatic.coBusiness process automation
CyberAttack.aiThreat detection and defense
Secure AI virtual data roomspuppyone
Puppyone is a Git-native platform that hosts context (documents, data, configurations) for AI agents with version control and file-level permissions. It exposes a shared Context Drive through multiple access points (CLI, MCP, REST API, Git, sandbox environments) so different agents can collaborate on shared knowledge with fine-grained security.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | puppyone-ai/puppyone |
| Owner | puppyone-ai |
| Primary language | TypeScript |
| License | Apache-2.0 — OSI-approved |
| Stars | 861 |
| Forks | 71 |
| Open issues | 26 |
| Latest release | v0.0.3 (2026-05-31) |
| Last updated | 2026-07-05 |
| Source | https://github.com/puppyone-ai/puppyone |
What puppyone is
Built on FastAPI (Python 3.12+) backend, Next.js 15 frontend, and Supabase PostgreSQL with S3/MinIO storage. Provides file-level security enforcement, Git-style checkout/commit workflows, Docker and E2B sandbox isolation, and task queuing via ARQ (Redis). Deployable as cloud-hosted or self-hosted Docker stack.
Get the puppyone source
Clone the repository and explore it locally.
git clone https://github.com/puppyone-ai/puppyone.gitcd puppyone# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Self-hosted Docker stack requires Docker daemon access on the host; for remote/multi-tenant deployments, the docs recommend E2B sandboxing instead of Docker socket sharing.
- Cloud deployments require Anthropic API key for agent chat; OAuth connectors (GitHub, Gmail, Google Drive) need provider credentials configured separately in backend environment.
- File-level security enforcement is built into the filesystem layer, but requires correct permission setup during agent provisioning; misconfiguration could expose unintended files.
- Git-style checkout/commit workflow introduces potential for merge conflicts and locking; agents must handle commit failures gracefully.
- MCP endpoint creation and API key distribution must follow your organization's secrets management practices; no automatic rotation or vault integration is mentioned.
When to avoid it — and what to weigh
- Single-agent or human-centric workflows — If your primary use case is human document collaboration, conventional file-sharing tools (Notion, Confluence, Drive) will be simpler. Puppyone's agent-level auth and versioning add overhead when not needed.
- Real-time collaborative editing for humans — Puppyone is designed for agent read/write patterns (checkout, commit, conflict resolution), not simultaneous human editing. No built-in CRDT or WebSocket-based live sync is documented.
- Production use without vendor support or SLA — The project is young (created Dec 2024, v0.0.3 as of latest release). Self-hosting requires operational expertise; cloud offering maturity and support terms are not stated in available data.
- Closed-source or proprietary deployments — Apache 2.0 requires source code disclosure for derivative works in network-accessible deployments in some interpretations. Internal legal review is recommended before wrapping Puppyone in a proprietary service.
License & commercial use
Licensed under Apache License 2.0. This is a permissive OSI license that permits use, modification, and distribution for any purpose (personal, commercial, open-source, proprietary), provided copyright notice and LICENSE file are preserved and significant modifications are documented.
Apache 2.0 permits commercial deployment and proprietary use. However, if Puppyone is modified and deployed as a network service, some interpretations of the AGPL-adjacent requirements (§5) may apply; legal review is recommended for SaaS offerings. Cloud-hosted Puppyone and self-hosted forks for internal use are unambiguously permitted. No commercial support, SLA, or warranty is stated in the available documentation.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | Medium |
File-level security is enforced at the filesystem layer; correctness depends on proper permission configuration. Local Docker Compose stack shares the host Docker daemon with the backend container, which carries sandbox escape risk; docs recommend E2B for remote/multi-tenant. Auth uses Supabase JWT + Access Keys; no mention of rate limiting, secret rotation, or audit log tamper-proofing. Self-hosted deployments inherit PostgreSQL, MinIO, and Redis security postures; hardening is operator responsibility. No penetration test or security audit results are disclosed.
Alternatives to consider
Langchain (LangSmith) or Anthropic Workbench
Simplified agent context management with less infrastructure overhead; better integration with specific model providers. Trade-off: less fine-grained file-level security and Git-style versioning.
Supabase + custom vector store (e.g., Pinecone, Weaviate)
If you only need RAG and context retrieval (not agent-facing file access), a database + vector store is simpler to deploy and maintain. Trade-off: no Git versioning, agent permissions, or multi-access-point abstractions.
Hugging Face Spaces or Modal for agent orchestration + cloud storage (S3, GCS)
Lightweight alternative for stateless agent workflows with minimal shared context. Trade-off: no file-level security, audit logging, or agent-centric permission model.
Build on puppyone with DEV.co software developers
Start with Puppyone Cloud (no infrastructure required) or self-host via Docker. Review the Apache 2.0 license and documentation to confirm fit for your use case.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
puppyone FAQ
Can I run Puppyone in production on-premises?
Does Puppyone support my existing auth system (SAML, Okta, etc.)?
What happens if two agents try to edit the same file concurrently?
Is there a cost to using the cloud version?
Custom software development, end to end
Standing up puppyone properly takes more than a deploy. As a software development agency, DEV.co handles the rag frameworks architecture, the web development on top, and the operational work underneath.
Ready to manage AI agent context at scale?
Start with Puppyone Cloud (no infrastructure required) or self-host via Docker. Review the Apache 2.0 license and documentation to confirm fit for your use case.