APACHE 2.0 / YOUR INFRASTRUCTURE

Self-host Snipara.Keep control.

Run the open-source context and memory engine on your infrastructure. Keep project documents, embeddings and decisions in your own database, with no Cloud account required.

Get the server on GitHub Enterprise support

Licensed under Apache 2.0 . Free server software. Optional paid deployment support.

DEPLOYMENT SIGNALReady to run

YOUR INFRASTRUCTURE

PostgreSQL + Redis + Snipara

DocsAgent

Start with ./scripts/quickstart.sh and keep the full project context loop close to the work.

01 / QUICKSTART

Up and running in three steps.

Choose the deployment shape that fits your environment, then connect the AI client your team already uses.

Get the open-source server

Clone the public repository. You do not need a Snipara Cloud account or approval to start.

git clone https://github.com/Snipara/snipara-server.git
cd snipara-server

Start your local workspace

With Docker running, the bootstrap starts PostgreSQL, Redis and Snipara, initializes a local workspace, and creates your local API key.

./scripts/quickstart.sh

Connect the AI client you already use

Use the local key created by setup in your MCP client. Keep the key private. The endpoint below is for a client on the same machine; use an authenticated HTTPS endpoint for remote access.

{
  "mcpServers": {
    "snipara": {
      "type": "http",
      "url": "http://localhost:8000/mcp/local",
      "headers": { "X-API-Key": "<SNIPARA_LOCAL_API_KEY>" }
    }
  }
}

02 / FULL ACCESS

Open-source core. No expiry.

The public server includes project-scoped context, semantic search, persistent memory and coordination tools without a trial or commercial license key. The Cloud dashboard, login, SaaS multi-tenancy, billing and commercial administration remain in the private Cloud application.

Public server capabilities, available indefinitely.

03 / ACCESS MODEL

Feature matrix.

Every self-hosted capability is available indefinitely. You run the software on your infrastructure and cover infrastructure, optional providers and operating costs.

Capability	Available
`snipara_ask`Quick documentation queries	Yes
`snipara_search`Regex pattern search	Yes
`snipara_context_query`Project-scoped context retrieval	Yes
`snipara_read`Read specific lines	Yes
`snipara_upload_document`Upload documents	Yes
`snipara_stats / snipara_sections`Browse indexed docs	Yes
`Session management`Inject, inspect, and clear context	Yes
`Semantic and hybrid search`Higher-recall retrieval modes	Yes
`snipara_decompose`Query decomposition	Yes
`snipara_multi_query`Batch queries	Yes
`snipara_plan`Execution planning	Yes
`Shared context and templates`Reusable context inside your local workspace	Yes
`Agent memory`Remember and recall project knowledge	Yes
`Multi-agent swarms`Coordinate multiple agents	Yes
`Code graph`Project structure, symbol context and impact tools	Yes

Self-hosted software is free; infrastructure is yours to operate.

Talk to us about deployment support

04 / WHY SELF-HOST

A boundary your team can reason about.

Self-hosting is for teams that need their project intelligence to stay close to their systems, policies, and operating model.

Data sovereignty

Store documents, embeddings and memories in your PostgreSQL database. Remote embedding providers and error reporting are optional operator choices.

Controls you operate

Manage access, backups, retention and monitoring under your own policies. Self-hosting alone does not certify a deployment or supply Cloud governance features.

Offline operation

Prepare images, dependencies and embedding models before disconnecting. Local operation requires no Snipara Cloud account or online license server.

Your infrastructure

Run PostgreSQL, optional Redis and your own monitoring. The public server authenticates with a local API key; Cloud login and SSO are separate.

Apache 2.0

Read, modify, redistribute and use the server commercially under Apache 2.0. The license does not grant rights to Snipara branding.

Docker-ready

Start with Docker Compose and move to the deployment model that fits your security and scale requirements.

05 / ENTERPRISE SUPPORT

Run it yourself. Get help when you need it.

The server is free to run. Support plans provide deployment help, priority response times, and an experienced partner for the infrastructure decisions around it.

Contact sales

Deployment scope, support coverage and pricing are agreed separately. A support agreement does not unlock software features or change the server license.

White-glove deployment

Hands-on setup and configuration support for your production environment.

Agreed support coverage

Define response targets and escalation channels in your support agreement.

Upgrade guidance

Plan version upgrades and data migrations for your installation.

Architecture reviews

Advice on scaling, performance tuning, and infrastructure optimization.

Capacity planning

Size your installation for the corpus and workload you need to serve.

Security maintenance

Agree on patch handling and maintenance responsibilities for your deployment.

06 / INFRASTRUCTURE

Size the system around your work.

Start small for evaluation, then separate the application, database, and cache tiers when the workload requires it.

START HERE

Local evaluation

Docker and Git

• Use the public repository quickstart
• Review the requirements of your chosen release

PostgreSQL + pgvector

• Persistent storage for your corpus
• Included in the local Compose stack

Redis and embeddings

• Redis is included in local Compose
• Prepare embedding models before offline use

FOR SCALE

Production planning

Access and monitoring

• Authenticated HTTPS for remote access
• Operator-managed keys, network controls and alerts

Capacity

• Measure indexing and query workloads
• Size memory, CPU and storage for your corpus

Data operations

• Backups with tested restores
• Versioned upgrades and migration checks
• Retention and maintenance policies

07 / DEPLOYMENT OPTIONS

Choose the shape that fits.

Simple

Docker Compose

The fastest path for a single-server deployment.

Local bootstrap script
Included in the repository

Tradeoff: Limited horizontal scalability

Complex

Kubernetes

An operator-managed option for teams that already run Kubernetes.

Use your existing platform
Control scheduling and resources

Tradeoff: You design and validate manifests, scaling and availability

Easy

PaaS

Use Render, Fly.io, or a similar managed platform.

Managed infrastructure
Easy scaling
Built-in monitoring

Tradeoff: Higher cost per query

Advanced

Custom cloud

Bring Snipara into your existing AWS, GCP, or Azure architecture.

Full control
Existing infrastructure integration
Cost optimization

Tradeoff: Requires a DevOps team

08 / HOSTED OR SELF-HOSTED

Choose what you want to operate.

Self-host when you want to operate the engine and its data. Choose Cloud for a managed service, a dashboard and workspace administration, with capacity and team governance according to your plan.

Start with Snipara Cloud Compare Cloud plans

Dimension	Hosted cloud	Self-hosted
Getting started	Create a Cloud account and connect your agent	Run the public quickstart
Software and service cost	Free and paid plans; see pricing	Free Apache 2.0 server; you pay operating costs
Infrastructure	Managed by Snipara	Your responsibility
Accounts and administration	Cloud dashboard and workspace administration	Local workspace and operator API key
Team governance	Available according to your Cloud plan	Cloud accounts, SSO and SaaS tenancy are not included
Updates and maintenance	Operated by Snipara	Your responsibility
Source code	Apache 2.0 core; private Cloud application	Apache 2.0 server
Offline operation	Requires access to the hosted service	Prepare dependencies and models first
Deployment support	According to your plan or agreement	Optional paid agreement

09 / FAQ

Questions before you deploy.

Is self-hosting really free?+

Yes. The public Apache 2.0 server is free to run with no commercial license key. You pay for infrastructure, any external providers you choose, and your operating time. Deployment support is optional.

Are any features time-limited?+

The public server has no trial window or commercial feature expiry. Its local context, search and memory capabilities remain available. Cloud administration, accounts, billing and SaaS multi-tenancy are separate products.

Does the server phone home?+

The public server does not require Snipara Cloud. Usage records, when enabled, stay in your PostgreSQL database. Remote embeddings and Sentry are opt-in; prepare dependencies and models in advance for offline operation.

What license is the code under?+

Snipara Server is licensed under Apache 2.0, including commercial use, modification, redistribution and operation as a hosted service, subject to the license terms. Snipara trademarks and branding are not licensed for reuse.

Can I mix hosted and self-hosted?+

You can operate both, but they are separate installations. The public server does not include Cloud accounts or automatically synchronize Cloud data. Plan any data transfer explicitly.

Do I need enterprise support?+

No. The self-hosted package includes the materials needed to run Snipara. Support is optional for teams that want hands-on deployment, priority SLAs, or architecture guidance.

Can I contribute to the project?+

Yes. Use the public GitHub repository and follow its contribution guide. Keep customer data, credentials and private Cloud code out of contributions.

READY WHEN YOU ARE

Give your team a project intelligence layer they own.

Start with the public server, or talk to us about operating it in your environment.

Get the server on GitHub Contact sales

Email: sales@starbox-group.com · Support: support@starbox-group.com