Synap for developers

Your technical context, in a pod you can program.

Architecture decisions, debug sessions, API research — captured from your editor and connected for you. Underneath: a typed API, an SDK, and an open-source backend you can self-host.

How developers use it

  1. Connect your coding agent

    Install the CLI and connect Claude Code, Cursor, Zed, Windsurf or another MCP client to your pod. The agent can read your context and write what it learns back — as proposals you review.

  2. Keep decisions, not just code

    Architecture decision records, debug notes with the fix, API docs you researched. A note about a rate limit gets linked to the API docs and the related issue.

  3. Program the pod

    A full tRPC API with scoped API keys, the Hub Protocol for agents, and @synap-core/sdk for TypeScript. Automate captures from CI, scripts, or your own tools.

  4. Run it where you want

    The pod stack (PostgreSQL, Typesense, pgvector, MinIO) ships as a Docker Compose setup. The same codebase runs managed pods and self-hosted ones.

Why developers choose Synap

  • Open source backend.

    Self-hosting is free: the backend source is public on GitHub. Read it, run it, extend it.
  • Your agent's memory, owned.

    What your coding agent learns lands in your pod, not in one vendor's chat history — switch agents and the context stays.
  • Real data access.

    PostgreSQL underneath: on a self-hosted pod, query it directly with any SQL client.

Common questions

How do developers use Synap?

Developers capture architecture decision records, debug sessions with their solutions, API documentation references, and meeting notes. They are connected for you — a debug note about a rate limit gets linked to the API docs and the related issue. The tRPC API lets you automate captures from CI pipelines, webhooks, and custom scripts.

Does Synap have an API for developers?

Yes. Synap exposes a full tRPC API with scoped API keys, the Hub Protocol for agent integration, an MCP endpoint, and @synap-core/sdk for TypeScript. Build custom tools, sync data from external services, or use Synap as the knowledge backend for your own applications. The pod runs PostgreSQL, so a self-hosted pod also gives you direct SQL access.

Can Synap replace Notion for developer documentation?

For a personal developer knowledge base, yes: Synap organizes technical captures for you instead of relying on manual structure. For team wikis and collaborative docs, Notion still has better multi-user editing. Synap excels as a personal technical record: ADRs, debug logs, API research, and project context, all linked.

Does Synap support self-hosting for developers?

Yes. The whole Synap pod stack (PostgreSQL, Typesense, pgvector, MinIO) is available as a Docker Compose configuration. Run it on any Linux VPS, home lab, or on-premise server. The same codebase runs managed and self-hosted pods.

Give your agent context that lasts.