OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Agent Memory & RAG

Puppyone

Puppyone is a Git-native context-hosting service for AI agents. It provides a shared context drive with Git version control, file-level permissions and access through tools including MCP, CLI, Git, bash/SSH and a web app.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Puppyone — OpenViST project profile in Agent Memory & RAG.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Puppyone when agent workflows need shared, versioned context with access scoped by agent, or when that context must be reachable through more than one tool interface.

Who it is for

  • Teams that need to maintain shared files and reference material for AI agents.
  • Developers connecting agent tools to a common context store through MCP, CLI or Git.
  • Operators who want a locally self-hosted context service using Docker.

Documented uses

  • Store and organize files or reference material in a shared agent context drive.
  • Manage versioned context with Git.
  • Give different agents scoped access to files.
  • Expose hosted context to MCP clients through an access point.
Before you choose

Requirements & limits

The README describes a hosted option that begins with creating an account and a Docker-based self-hosted option. It identifies Docker as the only prerequisite for the documented local deployment.

  • Access methods include CLI, MCP, Git, bash/SSH and the web app.
  • Web uploads and CLI webpage ingestion are documented ways to add content.
  • Self-hosted OAuth connectors require provider credentials in the backend environment.
  • The default local Docker sandbox shares the host Docker daemon with the backend; the README recommends E2B with an E2B_API_KEY for remote or multi-tenant deployments.
  • The public repository specifies the Apache-2.0 license and Python as its primary language.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Create a self-hosted Puppyone stack

Start the documented local Docker Compose stack.

Before you start

  • Docker
  • The Puppyone repository

Steps

  1. Clone the repository and change into its docker directory.

  2. Copy .env.example to .env.

  3. Run docker compose up --build -d --wait.

  4. When startup succeeds, open http://localhost:3000.

Expected outcome

The local stack starts with its frontend at http://localhost:3000.

Guide limitations

  • The first startup builds application images and may take several minutes.
  • The supplied configuration is for local use.
  • Existing PostgreSQL 15 data volumes require an explicit database upgrade; do not replace the image or delete volumes to make startup succeed.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
8 October 2026
Original website title
puppyone-ai/puppyone-cloud · Official homepage title · retained in its source language
How we review sourcesSuggest a correction