# Synapsor

Synapsor provides agent database change control for teams adding AI agents to existing Postgres and MySQL apps.

Keep your existing database as the source of truth. Risky agent-requested changes become evidence-backed write proposals with reviewable row diffs, a Synapsor review branch, approval or deterministic policy state, trusted-runner writeback, conflict results, and replay records.

For external Postgres/MySQL, Synapsor does not physically branch or merge the source database. Approved proposals become approved for writeback, then a customer-controlled trusted runner applies a guarded single-row update with its own write credential. For Synapsor-native tables, branch and merge are real Synapsor database operations.

Synapsor is a Supsmall Inc. product.

## Overview

Synapsor Cloud V2 is controlled beta software.

HTTP routes under /v1 are the stable API namespace for the V2 controlled-beta product.

The /v1 route prefix is not a V1 product label.

Free access remains invite-approved.

Builder Beta starts with a 14-day no-card trial for approved beta users, then continues at $20/month.

## Primary resources

- Database MCP commit safety: https://synapsor.ai/mcp
- Open-source local runner: https://synapsor.ai/open-source
- Local Docker MCP demo: https://synapsor.ai/demo/mcp-postgres
- Start here: https://synapsor.ai/docs/start-here
- Existing Postgres/MySQL live demo: https://synapsor.ai/demo/existing-db
- Write proposal demo: https://synapsor.ai/demo
- Quickstart: https://synapsor.ai/docs/quickstart
- Use Synapsor with your existing database: https://synapsor.ai/docs/existing-databases
- Open-source trusted runner: https://synapsor.ai/docs/open-source-runner
- Existing DB live demo docs: https://synapsor.ai/docs/existing-db-live-demo
- Existing DB UI setup wizard: https://synapsor.ai/docs/existing-db-ui-setup
- Existing database modes: https://synapsor.ai/docs/external-db-modes
- Existing DB 15-minute quickstart: https://synapsor.ai/docs/existing-db-quickstart
- Production single-node architecture: https://synapsor.ai/docs/production-single-node-architecture
- Production-oriented existing DB architecture: https://synapsor.ai/docs/existing-db-production-architecture
- Connect Postgres: https://synapsor.ai/docs/connect-postgres
- Connect MySQL: https://synapsor.ai/docs/connect-mysql
- Existing DB write proposals: https://synapsor.ai/docs/existing-db-write-proposals
- Existing DB security: https://synapsor.ai/docs/existing-db-security
- Find evidence later: https://synapsor.ai/docs/find-evidence-later
- AWS RDS and Aurora setup: https://synapsor.ai/docs/aws-rds-existing-db
- CDC roadmap, private preview only: https://synapsor.ai/docs/existing-db-cdc-roadmap
- External DB CDC roadmap, not current public connector path: https://synapsor.ai/docs/external-db-cdc
- CDC glossary: https://synapsor.ai/docs/external-db-cdc-glossary
- Postgres existing DB preview repo: https://github.com/sandeshtiwari/Synapsor-Postgres-CDC-Support-Demo
- MySQL existing DB preview repo: https://github.com/sandeshtiwari/Synapsor-Mysql-CDC-Ecommerce-Demo
- Prisma with Synapsor: https://synapsor.ai/docs/prisma-postgres-synapsor
- Drizzle with Synapsor: https://synapsor.ai/docs/drizzle-postgres-synapsor
- SQLAlchemy with Synapsor: https://synapsor.ai/docs/sqlalchemy-postgres-synapsor
- Django with Synapsor: https://synapsor.ai/docs/django-postgres-synapsor
- Rails with Synapsor: https://synapsor.ai/docs/rails-postgres-synapsor
- Value sources and lookup ids: https://synapsor.ai/docs/value-sources-and-handles
- Documentation index: https://synapsor.ai/docs
- Free vs Builder: https://synapsor.ai/docs/free-vs-builder
- Known limitations: https://synapsor.ai/docs/known-limitations
- Billing and cancellation: https://synapsor.ai/docs/billing-and-cancellation
- Agent workflows and run graphs: https://synapsor.ai/docs/agent-workflows
- Workflow examples: https://synapsor.ai/docs/workflow-examples
- External actions and outbox: https://synapsor.ai/docs/external-actions
- Agent evals and regression replay: https://synapsor.ai/docs/agent-evals
- Agent framework adapters: https://synapsor.ai/docs/agent-adapters
- Observability and traces: https://synapsor.ai/docs/observability-traces
- Token budgets and evidence lookup ids: https://synapsor.ai/docs/token-budgets-evidence-handles
- Agent syntax glossary: https://synapsor.ai/docs/agent-syntax-glossary
- Settlement policies: https://synapsor.ai/docs/settlement-policies
- Storage profiles: https://synapsor.ai/docs/storage-profiles
- Table constraints: https://synapsor.ai/docs/table-constraints
- Auto-branching: https://synapsor.ai/docs/auto-branching
- System views: https://synapsor.ai/docs/system-views
- SQL extensions: https://synapsor.ai/docs/sql-extensions
- CLI status: https://synapsor.ai/docs/cli-status
- CLI quickstart: https://synapsor.ai/docs/cli-quickstart
- Browser Console: https://synapsor.ai/docs/browser-console
- Expense Guard lab: https://synapsor.ai/docs/expense-guard-lab
- Contract-to-Cash lab: https://synapsor.ai/docs/contract-to-cash-lab
- Examples: https://synapsor.ai/examples
- Support refund agent example: https://synapsor.ai/examples/support-ticket-evidence
- Existing Postgres support agent example: https://synapsor.ai/examples/existing-postgres-support-agent
- Existing MySQL ecommerce agent example: https://synapsor.ai/examples/existing-mysql-ecommerce-agent
- E-commerce order assistant example: https://synapsor.ai/examples/order-assistant-workflow
- Analytics metric agent example: https://synapsor.ai/examples/metric-definition-agent
- RAG policy workflow example: https://synapsor.ai/examples/policy-rag-workflow
- GitHub PR workflow example: https://synapsor.ai/examples/github-pr-workflow
- Voice call-center workflow example: https://synapsor.ai/examples/voice-call-center-workflow
- Prompt-injection receipt guardrail example: https://synapsor.ai/examples/prompt-injection-receipt-guardrail
- Pricing: https://synapsor.ai/pricing
- Support: https://synapsor.ai/support
- Security: https://synapsor.ai/security
- Terms: https://synapsor.ai/terms
- Privacy: https://synapsor.ai/privacy
- Refunds: https://synapsor.ai/refunds
- Control plane OpenAPI: https://synapsor.ai/openapi.json
- Full LLM context: https://synapsor.ai/llms-full.txt

## Current beta plans

### Free Controlled Beta / Private Beta Sandbox

- Price: $0
- Access: invite-approved only
- Overage behavior: hard-capped, no usage overages
- Project limit: 1 project
- Database limit: 1 database per project
- Storage counter: 1 GB
- Branch limit: 2 branches
- Capability invocation limit: 1,000/month
- Embedding call limit: 1,000/month
- Backup retention target: 1 day
- Spend cap: $0

### Builder Beta

- Price: $20/month
- Trial: 14-day no-card Builder Trial
- Access: approved beta account
- Overage behavior: no usage overages by default
- Project limit: 3 projects
- Database limit: 3 databases per project
- Storage counter: 10 GB
- Branch limit: 10 branches
- Capability invocation limit: 50,000/month
- Embedding call limit: 50,000/month
- Backup retention target: 7 days
- Billing gate: Builder resource creation requires billing state active or trialing
- Trial end: missing payment method pauses Builder access without deleting data
- CDC: private preview only; disabled during Builder Trial

### Request-only plans

- Scale/PAYG: request-only / coming later
- Enterprise: manual conversation only
- Builder is the only active paid beta plan
- Builder Trial starts when a Builder-approved invite is accepted; paid checkout is used only to continue after the trial or resume paid Builder access
- Free Controlled Beta remains invite-approved

## Public surface

- SQL execution through /v1/sql
- Control-plane calls through /v1/control
- /v1 is the stable HTTP API namespace, not the hosted-product version
- Synapsor CLI through the @synapsor/client package
- Browser Console for signed-in SQL/capability/evidence/proposal/replay actions
- External Postgres and MySQL read-only connectors for selected tables/views, least-privilege source users, SESSION-bound tenant filters, generated capabilities, evidence, and external query audit.
- External DB proposal writeback uses Synapsor write proposals plus a trusted runner; the model never writes raw SQL and approved updates use parameterized SQL with primary-key, tenant, idempotency, and conflict guards.
- External-source CLI commands: synapsor sources create postgres, sources create mysql, sources test, sources inspect, sources import, sources generate, sources list, sources show, sources doctor, sources disable.
- Existing database modes: live-read is the public connector path today; write proposals are a reviewed writeback workflow through a trusted worker; CDC/mirrored subsets are private preview/hardening only and are not customer-production supported.
- AWS external DB smoke is guarded by RUN_AWS_EXTERNAL_DB_TESTS=1 and uses scripts/smoke-external-db-aws.py with RDS/Aurora source URLs supplied through environment variables.
- RDS smoke is dev/test only, disabled by default, can cost money if left running, and must be verified clean after tests.
- Agent framework boundary: LangGraph, OpenAI Agents SDK, CrewAI, MCP, or your own loop can handle routing; Synapsor keeps durable records for scoped reads, evidence, proposals, native branch staging or external review branches, approval, settlement, and replay.
- Existing database framing: keep Postgres/MySQL as source of truth, and put Synapsor between agents and production writes so the model gets approved tools instead of raw SQL.
- CREATE AGENT WORKFLOW records the enforceable database contract for a business run: trusted session requirements, allowed capabilities/actions, evidence rules, Synapsor-native branch-staged writes or external review-branch proposals, memory policy, retention, and replay.
- Treat the framework graph as routing and the Synapsor workflow as the governed database record for steps that read, write, remember, call side effects, or need audit later.
- Use workflows as governed records for business processes. A refund or support workflow can require trusted session keys, approved capabilities, evidence, write proposals, approval rules, idempotent side-effect intents, checkpoints, retention, and replay without forcing the app to abandon its agent framework.
- Prefer approved high-level workflow capabilities and compact Synapsor handles over rebuilding tenant, policy, evidence, proposal, branch, and approval state in every prompt.
- Synapsor workflows do not replace LangGraph, OpenAI Agents SDK, CrewAI, MCP, or custom planners. Those systems can keep routing; Synapsor governs sensitive database-backed steps.
- Synapsor does not claim outside API calls can be rolled back by a DB transaction. External actions are durable intents claimed by trusted workers with idempotency keys and confirmed back into the run graph.
- Sessions
- Agent contexts
- Agent capabilities
- Agent workflows and durable run graphs
- Workflow contracts can require trusted session fields, cap steps/tool calls, and restrict allowed capabilities or external actions for a run.
- Workflow contracts can persist native auto-branch templates or external review-branch proposal state, risk approval rules, retry/error handling, and run/evidence/payload retention windows.
- Expose fewer, safer tools to the model: answer with evidence, propose a write, queue an approved external action, settle a run, and inspect replay records instead of exposing raw provider/update/audit primitives.
- Workflow glossary: Agent workflow = the database-side contract for a business run; Agent run = one execution returned by BEGIN AGENT RUN or SDK start; Run graph = ordered durable steps/edges/resources; Step key = developer-provided step name inside a run.
- Workflow artifacts: Evidence bundle = durable why trail; Proposal = staged write/change; Settlement = policy-controlled approve/commit/merge/reject/hold decision for Synapsor-native data or approved-for-writeback decision for external DB targets; Adapter = approved capability/workflow mapping to MCP, OpenAI Agents SDK, LangGraph, CrewAI, or custom tools.
- Workflow REST API: POST /v1/agent/workflows, POST /v1/agent/runs, POST /v1/agent/runs/steps, POST /v1/agent/runs/checkpoints, POST /v1/agent/runs/guardrail-events, POST /v1/agent/runs/handoffs, POST /v1/agent/runs/interrupts, POST /v1/agent/runs/complete, POST /v1/agent/runs/explain, POST /v1/agent/runs/settle
- Workflow SQL helpers: CREATE AGENT WORKFLOW, CREATE SETTLEMENT POLICY ... FOR WORKFLOW, BEGIN AGENT RUN, INVOKE AGENT CAPABILITY ... IN AGENT RUN, RECORD AGENT STEP, RECORD AGENT GUARDRAIL EVENT, HANDOFF AGENT RUN, INTERRUPT AGENT RUN, SETTLE AGENT RUN, END AGENT RUN, EXPLAIN AGENT RUN
- Workflow settlement policies can combine JSON_VALUE(run.output, '$.field') run-output checks with PAYLOAD checks on each linked write proposal.
- SETTLE AGENT RUN preflights authorization and duplicate target effects across linked proposals before auto-commit mutation, so conflicting workflow proposals remain staged for review.
- Python workflow SDK: db.agent_runs.start(...), run.invoke_capability(...), run.propose_external_action(...), db.external_actions.approve(...), run.checkpoint(...), run.complete(...), run.explain(...), db.external_actions.claim(...), db.evals.run(...)
- Node workflow SDK: db.agentRuns.start(...), run.invokeCapability(...), run.proposeExternalAction(...), db.externalActions.approve(...), run.checkpoint(...), run.complete(...), run.explain(...), db.externalActions.claim(...), db.evals.run(...)
- External action outbox for Stripe/Zendesk/email-style side effects
- External action claims record the worker principal; confirmation from a different active worker principal is rejected.
- External action REST API: POST /v1/agent/external-actions/propose, POST /v1/agent/external-actions/{action_instance_id}/approve, POST /v1/agent/external-actions/claim, POST /v1/agent/external-actions/{action_instance_id}/confirm
- External action SQL helpers: CREATE EXTERNAL ACTION, PROPOSE EXTERNAL ACTION, APPROVE EXTERNAL ACTION, CLAIM EXTERNAL ACTION, CONFIRM EXTERNAL ACTION
- External action confirmations require an active unexpired worker claim; expired claims must be reclaimed before confirmation.
- Agent evals for regression replay over stored workflow runs and source-table dataset rows
- Agent eval REST API: POST /v1/agent/evals, POST /v1/agent/evals/run, POST /v1/agent/evals/failures, POST /v1/agent/evals/diff
- Agent eval SQL helpers: CREATE AGENT EVAL, CREATE AGENT EVAL ... SOURCE TABLE, RUN AGENT EVAL, SHOW AGENT EVAL FAILURES, DIFF AGENT EVAL
- Dataset-table eval assertions can compare JSON_VALUE(output, '$.field') to ROW expected_column values.
- Agent eval SDK helpers can create run-history evals or source-table dataset evals with Python source_table and Node sourceTable.
- Governed memory evolution policies for conflict detection, supersession, memory events, and run-scoped recall
- Memory evolution SQL helpers: CREATE MEMORY POLICY, SHOW MEMORY CONFLICTS, SUPERSEDE MEMORY FACT, RECALL MEMORY ... AS OF AGENT RUN
- Agent framework adapters for MCP/OpenAI/LangGraph-style tools generated from approved capabilities
- Adapter modes: expose individual approved capabilities as safe tools, or expose a whole workflow as one safe tool with EXPOSE WORKFLOW.
- Workflow-as-tool adapter responses return Synapsor-produced ids such as run_id, evidence_bundle_id, proposal_id, branch, status, and next_allowed_actions.
- Adapter REST API: POST /v1/agent/adapters, POST /v1/agent/adapters/tools, POST /v1/agent/adapters/call-tool
- Adapter SQL helper: CREATE AGENT ADAPTER
- Observability trace API: POST /v1/agent/runs/trace
- Observability SQL helpers: SHOW TRACE FOR AGENT RUN, SHOW SLOW AGENT CAPABILITIES, SHOW TOKEN USAGE, SHOW APPROVAL LATENCY, CREATE OBSERVABILITY SINK
- Hidden bindings
- Governed memory
- Evidence bundles
- Branches and auto-branching
- Write proposals and settlement policies
- Replay / agent time travel
- Replay API: POST /v1/agent/runs/replay
- Replay SQL helpers: AS OF AGENT RUN for historical reads, and CREATE BRANCH ... FROM main AS OF AGENT RUN for writable investigation branches
- RBAC/security policies
- Hybrid search
- Token budgets, inline evidence, and compact evidence lookup records
- Agent syntax glossary for ARG, BINDING, TENANT, OPERATION, PLAN, PAYLOAD, and EVIDENCE
- Table constraints and foreign keys
- Storage profiles for hot state, reference data, append logs, audit logs, searchable knowledge, and columnar archives
- Capability plans
- Agent catalog/introspection
- System views for catalog, workflow, run graph, external action, security, and storage metadata
- Run graph views: synapsor_agent_workflows, synapsor_agent_workflow_runs, synapsor_agent_run_steps, synapsor_agent_run_edges
- External action views: synapsor_external_actions, synapsor_external_action_events
- Eval views: synapsor_agent_eval_suites, synapsor_agent_eval_runs, synapsor_agent_eval_results
- Memory views: synapsor_memory_policies, synapsor_memory_events
- Adapter views: synapsor_agent_adapters, synapsor_agent_adapter_tools
- Observability views: synapsor_observability_sinks
- Retention/archive DDL
- Compact evidence/resource ids
- Branch create/diff/merge workflows
- Project workflows
- Database workflows
- API key workflows
- Billing workflows
- Backup-status workflows
- Operator-controlled restore workflows
- Plan metering counts capability invocations, not hosted autonomous agent loops.

## Value sources for examples

- Developer-defined values: table names, column names, context names, capability names, policy names, explicit branch names, project ids, and database names.
- Backend/session-defined values: SESSION tenant_id, principal, current object ids, entitlement ids, active thread/case ids, and API keys from the dashboard.
- Caller-defined values: ARG values supplied through INVOKE/PROPOSE JSON bodies, Python SDK args, Node SDK args, or HTTP request bodies.
- Synapsor-produced values: agent_run_id, run_resource, evidence_bundle, proposal lookup ids such as wrp://1, evidence lookup records such as evidence://bundle/1, ctx:// resource records, and auto-created branch_name values.
- Convenience aliases: last_context, last_evidence, and last_proposal are current shell/session shortcuts. Production apps should store durable returned ids with their app audit row and query system views or Workspace Activity when needed.
- System views for lookup: synapsor_agent_activity for normalized run/evidence/proposal/replay search; synapsor_evidence_bundles and synapsor_evidence_resources for evidence bundle/resource inspection; synapsor_replay_records for replay handles plus branch_kind/proposal_target_kind/writeback_status; synapsor_query_audit for query fingerprints/source reads; synapsor_agent_runs for run ids plus branch_kind/proposal_count/external_writeback_count; synapsor_agent_write_proposals or synapsor_write_proposals for proposal ids plus target_kind/branch_kind/source_database_mutated/writeback_status/trusted_worker_required; synapsor_agent_resources and synapsor_agent_settlement_events for lower-level records.
- Native lookup SQL: SELECT ... FROM AGENT ACTIVITY WHERE tenant_id = 'acme' AND business_object_id = 'T-1042' ORDER BY created_at DESC LIMIT 50.
- Evidence-focused native lookup SQL: INSPECT AGENT EVIDENCE WHERE tenant_id = 'acme' AND business_object_id = 'T-1042' ORDER BY TIME DESC LIMIT 50. TIME maps to the durable created_at lookup column.
- Comment syntax: Synapsor SQL examples use -- comments. The parser also accepts # line comments and /* ... */ block comments. Shell snippets use # comments.

## Replay and time travel syntax

- Implemented replay endpoint: POST /v1/agent/runs/replay
- Required replay body fields: run_id integer and session object
- run_id comes from the agent_run_id returned by a prior capability invocation or from synapsor_agent_runs.
- Default replay mode: deterministic_persisted_replay
- Other read-only comparison modes: original_snapshot, current, version, timestamp, branch
- version mode requires version
- timestamp mode requires timestamp
- branch mode requires branch_name
- Write/proposal capabilities should be investigated by creating a branch from the agent-run snapshot instead of mutating during replay.

```http
POST /v1/agent/runs/replay
Authorization: Bearer <database-api-key>
Content-Type: application/json

{
  "run_id": 123,
  "session": {
    "tenant_id": "acme",
    "principal": "auditor_01"
  },
  "mode": "deterministic_persisted_replay"
}
```

```sql
AS OF AGENT RUN '123'
SELECT * FROM expenses WHERE expense_id = 'EXP-1001';

CREATE BRANCH review_run_123
FROM main AS OF AGENT RUN '123';
```

## Demo-specific measurements

- Expense Guard Labs is demo-specific, not a general database benchmark.
- Expense Guard source: controlled demo measurements on 2026-05-19.
- Expense Guard scope: five comparable OpenAI Agents SDK cases.
- Expense Guard result: 58.4% fewer average input tokens for the Synapsor lane.
- Expense Guard result: 86.5% less app-owned glue LOC for the Synapsor lane.
- Contract-to-Cash source: seeded demo metrics.
- Contract-to-Cash result: 78.8% fewer average input tokens for the Synapsor lane.
- Contract-to-Cash result: 83.0% less app-owned glue LOC for the Synapsor lane.
- Product framing: Synapsor keeps repeated context, policy retrieval, evidence, proposal state, branches, approval, and replay in durable Synapsor records.
- Existing DB live demo: https://synapsor.ai/demo/existing-db shows live-read Postgres/MySQL mappings with evidence, query audit, proposals, and writeback status using seeded demo-only sources.
- Existing DB guided demo: https://synapsor.ai/demo/existing-db walks through source registration, safe mapping import, generated context/capability/workflow safety contracts, concrete evidence rows, query audit, write proposal, writeback boundary, and replay inspection for both Postgres and MySQL.
- Existing DB guided demo starts with a source preview: seeded Postgres/MySQL rows on one side, Synapsor-visible mapped columns, denied fields, trusted SESSION values, and generated contract names on the other.
- Existing DB guided demo results are summary-first: after a run, the page shows source, rows read, tables touched, kept-out review fields, Raw SQL access: No, Source DB changed: No, proposal/writeback status, and replay availability before advanced handles.
- Existing DB guided demo keeps technical handles collapsed under Advanced sections; users inspect readable row data, query audit, write proposal, writeback boundary, and replay status first.
- Existing DB guided demo MySQL lane is read-only in the public seeded visitor experience; signed-in workspaces can configure MySQL proposal writeback mappings separately.
- Existing DB guided demo MySQL summary explicitly shows Write proposal: No, Source DB changed: No, and Raw SQL access: No for the public seeded visitor lane.
- Signed-in Sources wizard status states: live_read_ready, mapping_required, proposal_ready, writeback_not_configured, writeback_dry_run_required, writeback_enabled, cdc_private_preview, connection_failed, credentials_missing, permission_error.
- Signed-in Sources wizard empty states are safe by default: no source, source with no imported mappings, mappings without a generated contract, and live-read without proposal/writeback each explain the next action and link to docs or the seeded demo.
- Signed-in Sources wizard proposal approval fails closed when writeback is not configured, dry-run/readiness evidence is missing, permissions are locked, or the proposal is terminal. Reject/request-changes never mutates the external database.
- Signed-in Sources wizard replay reads stored evidence/audit/proposal/checkpoint state and does not rerun external side effects unless explicitly requested by a trusted worker.
- Write proposal demo: https://synapsor.ai/demo compares Postgres app glue with Synapsor workflow records using seeded data.
- Write proposal demo results are summary-first: request, decision, risk lane, Source DB changed: No, write proposal, branch/replay availability, evidence count, seeded token comparison, app-glue LOC, DB/API round trips, and approval state appear before the lane details.
- Write proposal demo run states are explicit: not run yet, running seeded workflow, seeded request out of scope, rate-limited, validation/backend error, success, and reset. Public review/approval controls are simulations and do not mutate production/customer data.
- Prompt-injection framing: untrusted receipt, ticket, document, and message text is evidence, not authority; tenant scope, write targets, approval, and replay remain enforced by Synapsor.
- Claim boundary: the demo metrics are not general speed claims and do not guarantee token savings for every workload.

## Claim boundaries

- Hosted V2 is controlled-beta software.
- Hosted V2 is single-node.
- No serverless storage separation claim.
- No high-availability claim.
- No SLA claim.
- No compliance attestation claim.
- No horizontal-scaling claim.
- No usage overages by default.
- Free access requires invite approval during controlled beta.
- Scale/PAYG and Enterprise remain request/manual only.
- Demo metrics are controlled measurements, not general database benchmarks.

## Contact

- Support: support@synapsor.ai
- Security: security@synapsor.ai
- Billing: billing@synapsor.ai
- General: hello@synapsor.ai

## Complete documentation index

- What is Synapsor?
  URL: https://synapsor.ai/docs/what-is-synapsor
  Summary: Synapsor is an agent access-control layer for existing Postgres/MySQL data and production write proposals.
- Start here
  URL: https://synapsor.ai/docs/start-here
  Summary: A short mental model for how Synapsor differs from a normal database, vector database, or agent framework.
- Database MCP commit safety
  URL: https://synapsor.ai/docs/mcp
  Summary: MCP connects the agent. Synapsor controls the database commit boundary.
- MCP quickstart
  URL: https://synapsor.ai/docs/mcp-quickstart
  Summary: Start with the local open-source runner, then connect Cloud when you need team approval and hosted replay.
- Local MCP runtime
  URL: https://synapsor.ai/docs/mcp-local-runtime
  Summary: Run Synapsor Runner locally without a Cloud account, API key, billing, or hosted workspace.
- Cloud-linked MCP mode
  URL: https://synapsor.ai/docs/mcp-cloud-mode
  Summary: Cloud mode keeps write credentials local while moving approvals, policy, evidence, replay, and runner visibility into Synapsor Cloud.
- Read-only and shadow mode
  URL: https://synapsor.ai/docs/mcp-shadow-mode
  Summary: Read-only and shadow modes let teams test MCP database workflows before enabling guarded writeback.
- Semantic MCP tools
  URL: https://synapsor.ai/docs/mcp-semantic-tools
  Summary: Use semantic tools such as billing.propose_late_fee_waiver instead of execute_sql.
- MCP trusted context
  URL: https://synapsor.ai/docs/mcp-trusted-context
  Summary: Trusted context comes from backend auth, Cloud session, or runner environment, not model arguments.
- MCP write proposals
  URL: https://synapsor.ai/docs/mcp-write-proposals
  Summary: A write tool creates an evidence-backed proposal; it does not directly change Postgres or MySQL.
- MCP trusted runner and conflict detection
  URL: https://synapsor.ai/docs/mcp-trusted-runner
  Summary: The trusted runner executes approved writeback jobs and refuses stale proposals.
- MCP stale-row conflict detection
  URL: https://synapsor.ai/docs/mcp-conflict-detection
  Summary: The demo moment: the business state changed after the agent saw it, so Synapsor refused to commit.
- MCP replay
  URL: https://synapsor.ai/docs/mcp-replay
  Summary: Replay shows what the agent saw, what it proposed, who approved it, what the runner attempted, and what happened.
- Static MCP database risk review
  URL: https://synapsor.ai/docs/mcp-audit
  Summary: `synapsor mcp audit` is a static risk review for database-facing MCP tool manifests, not a security guarantee.
- MCP security boundary
  URL: https://synapsor.ai/docs/mcp-security-boundary
  Summary: Synapsor constrains the database state transition; it does not make all MCP usage secure.
- MCP client setup
  URL: https://synapsor.ai/docs/mcp-client-setup
  Summary: After the Docker demo passes, attach a local MCP client through tested stdio config shapes.
- Agent workflows and run graphs
  URL: https://synapsor.ai/docs/agent-workflows
  Summary: Use your agent framework for planning. Use Synapsor for the workflow contract: allowed capabilities, trusted session fields, evidence, native branches or external review branches, external actions, approvals, and replay.
- Workflow examples
  URL: https://synapsor.ai/docs/workflow-examples
  Summary: See how the same agent projects people already build with frameworks become safer, more replayable, and easier to approve when the workflow contract lives in Synapsor.
- Agent evals and regression replay
  URL: https://synapsor.ai/docs/agent-evals
  Summary: Replay stored workflow runs against JSON, evidence, proposal, and approval assertions before changing policy or capability behavior.
- Agent framework adapters
  URL: https://synapsor.ai/docs/agent-adapters
  Summary: Expose reviewed Synapsor capabilities as safe tools for MCP, OpenAI Agents SDK, LangGraph, CrewAI, or your own loop.
- Observability and traces
  URL: https://synapsor.ai/docs/observability-traces
  Summary: Debug a workflow from request to capability, evidence, proposal, external action, approval, and replay.
- External actions and outbox
  URL: https://synapsor.ai/docs/external-actions
  Summary: Record Stripe, Zendesk, email, Slack, or other external side-effect intents durably before a trusted worker executes them.
- Value sources and lookup ids
  URL: https://synapsor.ai/docs/value-sources-and-handles
  Summary: Learn which example values you choose, which values your app sets in session, and which lookup ids or resource records Synapsor returns.
- Free vs Builder
  URL: https://synapsor.ai/docs/free-vs-builder
  Summary: Compare the two active V2 controlled-beta plans and their hard limits.
- Storage profiles
  URL: https://synapsor.ai/docs/storage-profiles
  Summary: Choose row, log, searchable, and archive-oriented table behavior for agent-native workloads.
- Table constraints and foreign keys
  URL: https://synapsor.ai/docs/table-constraints
  Summary: Synapsor enforces the relational integrity constraints that agent workflows should not be allowed to improvise.
- Auto-branching
  URL: https://synapsor.ai/docs/auto-branching
  Summary: Proposal-capable invocations can create isolated branches automatically so risky writes never touch main first.
- Capability plans
  URL: https://synapsor.ai/docs/capability-plans
  Summary: Composed capability plans let Synapsor prepare memory, searches, lookups, rules, payloads, and evidence inside the database.
- Agent time travel
  URL: https://synapsor.ai/docs/agent-time-travel
  Summary: Historical reads, run replay, and branches from prior snapshots show what an agent saw and what changed later.
- Agent catalog and introspection
  URL: https://synapsor.ai/docs/agent-catalog-introspection
  Summary: Inspect, version, migrate, and read resources produced by agent contexts and capabilities.
- System views
  URL: https://synapsor.ai/docs/system-views
  Summary: Query Synapsor catalog, workflow, security, and storage metadata without scraping logs.
- SQL extensions
  URL: https://synapsor.ai/docs/sql-extensions
  Summary: A map of Synapsor syntax that goes beyond ordinary SQL.
- Existing database modes: live-read, write proposals, and CDC preview
  URL: https://synapsor.ai/docs/external-db-modes
  Summary: Start with live-read external mappings. Add proposal writeback after the read path works. Treat CDC mirrored subsets as private preview hardening, not customer-production support.
- External DB CDC glossary
  URL: https://synapsor.ai/docs/external-db-cdc-glossary
  Summary: Plain-English definitions for CDC, mirrors, snapshots, checkpoints, source positions, lag, capture age, retention, fail closed, cleanup proof, soak, RDS smoke, and P0/P1 incidents.
- UI setup for existing Postgres/MySQL
  URL: https://synapsor.ai/docs/existing-db-ui-setup
  Summary: Use the workspace Sources wizard when you want to connect your own read-only Postgres/MySQL source without hand-writing Synapsor syntax first.
- Existing database live demo
  URL: https://synapsor.ai/docs/existing-db-live-demo
  Summary: A public seeded demo that shows Synapsor working beside an existing Postgres/MySQL database without migration, raw SQL tools, or production CDC.
- Use Synapsor with your existing database
  URL: https://synapsor.ai/docs/existing-databases
  Summary: Keep Postgres or MySQL as your source of truth. Synapsor adds the agent-safe layer: trusted session bindings, governed context, reviewed capabilities, evidence, audit, and replay.
- Production single-node architecture
  URL: https://synapsor.ai/docs/production-single-node-architecture
  Summary: Synapsor Cloud is controlled beta today. This page separates the current hosted beta, the production-grade single-node architecture being hardened, and future distributed/serverless work.
- Production-oriented single-node architecture for existing databases
  URL: https://synapsor.ai/docs/existing-db-production-architecture
  Summary: Current Synapsor Cloud is controlled beta. The production-oriented architecture keeps Postgres/MySQL as source of truth and uses Synapsor for contracts, evidence, proposals, replay, and audit.
- Connect an existing database in 15 minutes
  URL: https://synapsor.ai/docs/existing-db-quickstart
  Summary: Create a least-privilege source user, connect Postgres/MySQL, inspect schema, import selected tables, generate a capability, bind SESSION values, invoke it, and inspect evidence.
- Connect Postgres
  URL: https://synapsor.ai/docs/connect-postgres
  Summary: Connect selected Postgres tables/views to Synapsor in read-only live mode with least-privilege credentials and tenant-scoped generated capabilities.
- Connect MySQL
  URL: https://synapsor.ai/docs/connect-mysql
  Summary: Connect selected MySQL tables/views to Synapsor in read-only live mode with least-privilege credentials and tenant-scoped generated capabilities.
- CDC roadmap and mirrored subsets
  URL: https://synapsor.ai/docs/external-db-cdc
  Summary: CDC/mirrored subsets are private preview/hardening work. Current public connectors use live-read external mappings while Postgres/MySQL remains the source of truth.
- Existing DB CDC roadmap
  URL: https://synapsor.ai/docs/existing-db-cdc-roadmap
  Summary: The current public path is live-read external mappings. CDC/mirrored subsets are private preview/hardening work that needs production monitoring, cleanup, and signoff before broader use.
- Existing DB security model
  URL: https://synapsor.ai/docs/existing-db-security
  Summary: How Synapsor keeps existing Postgres/MySQL access least-privilege, tenant-scoped, audited, and free from raw model SQL access.
- Open-source trusted runner
  URL: https://synapsor.ai/docs/open-source-runner
  Summary: Apply approved Postgres/MySQL write proposals inside your environment.
- Existing DB write proposals
  URL: https://synapsor.ai/docs/existing-db-write-proposals
  Summary: Agents do not write directly to your Postgres or MySQL database. They create evidence-backed Synapsor proposals that a trusted worker applies after approval.
- AWS RDS and Aurora setup
  URL: https://synapsor.ai/docs/aws-rds-existing-db
  Summary: Use staging first, least-privilege read-only credentials, SSL, low row limits, and source health checks before connecting RDS or Aurora databases.
- Prisma with Synapsor
  URL: https://synapsor.ai/docs/prisma-postgres-synapsor
  Summary: Keep Prisma for normal app reads/writes. Use Synapsor for agent-facing capabilities, evidence, proposals, and replay.
- Drizzle with Synapsor
  URL: https://synapsor.ai/docs/drizzle-postgres-synapsor
  Summary: Keep Drizzle for typed app queries while Synapsor governs agent reads, evidence, proposals, and replay.
- SQLAlchemy with Synapsor
  URL: https://synapsor.ai/docs/sqlalchemy-postgres-synapsor
  Summary: Keep SQLAlchemy for your Python app while Synapsor governs agent-facing data access and proposal workflows.
- Django with Synapsor
  URL: https://synapsor.ai/docs/django-postgres-synapsor
  Summary: Keep Django ORM for the web app and use Synapsor for agent-safe reads, proposals, approvals, and replay.
- Rails with Synapsor
  URL: https://synapsor.ai/docs/rails-postgres-synapsor
  Summary: Keep ActiveRecord for Rails and use Synapsor for reviewed agent capabilities, evidence, proposals, and replay.
- Known limitations
  URL: https://synapsor.ai/docs/known-limitations
  Summary: Hosted V2 controlled beta is useful for evaluation, but its boundaries are explicit.
- Billing and cancellation
  URL: https://synapsor.ai/docs/billing-and-cancellation
  Summary: How Builder Beta billing, entitlement state, cancellation, and no-overage behavior work.
- Create a project
  URL: https://synapsor.ai/docs/create-project
  Summary: Projects group databases, quotas, billing state, usage, backups, and audit events.
- Create a database
  URL: https://synapsor.ai/docs/create-database
  Summary: A database provisions a runtime branch on the hosted single-node Synapsor runtime.
- Connect with Python
  URL: https://synapsor.ai/docs/connect-python
  Summary: Use the Python SDK for agent and SQL workflows from Python applications.
- Connect with Node.js
  URL: https://synapsor.ai/docs/connect-node
  Summary: Use the Node SDK for TypeScript and JavaScript apps.
- Create your first agent context
  URL: https://synapsor.ai/docs/create-first-agent-context
  Summary: Agent contexts bind hidden session values, SQL reads, hybrid search, and memory into replayable inputs.
- Inspect evidence
  URL: https://synapsor.ai/docs/inspect-evidence
  Summary: Evidence bundles explain exactly what a capability invocation read and why it was allowed.
- Agent contexts
  URL: https://synapsor.ai/docs/agent-contexts
  Summary: Agent contexts define the read model an agent is allowed to use.
- Agent capabilities
  URL: https://synapsor.ai/docs/agent-capabilities
  Summary: Capabilities expose approved agent actions over a context with explicit modes and evidence policy.
- Token budgets and evidence lookup records
  URL: https://synapsor.ai/docs/token-budgets-evidence-handles
  Summary: Shape capability responses so agents get compact handles instead of repeated prompt-stuffed context.
- Agent syntax glossary
  URL: https://synapsor.ai/docs/agent-syntax-glossary
  Summary: A concise glossary for Synapsor-specific SQL extensions that are not standard SQL.
- Hidden session bindings
  URL: https://synapsor.ai/docs/hidden-session-bindings
  Summary: Hidden bindings let the application pass trusted context that prompts and users cannot override.
- Governed memory
  URL: https://synapsor.ai/docs/governed-memory
  Summary: Memory facts are scoped, evidenced, approved, retired, and replayable.
- Evidence bundles
  URL: https://synapsor.ai/docs/evidence-bundles
  Summary: Evidence bundles make agent answers, proposals, and replays inspectable.
- Find evidence later
  URL: https://synapsor.ai/docs/find-evidence-later
  Summary: How humans find the exact run, evidence bundle, proposal, approval, settlement, and replay record after many agent reads or writes.
- Agent Activity
  URL: https://synapsor.ai/docs/agent-activity
  Summary: Search agent runs, evidence bundles, proposals, replay records, query fingerprints, and business objects from one normalized lookup surface.
- Branching modes
  URL: https://synapsor.ai/docs/branching-modes
  Summary: Synapsor-native data uses real branch/merge. Existing Postgres/MySQL uses Synapsor review branches and trusted writeback.
- Branches
  URL: https://synapsor.ai/docs/branches
  Summary: Branches isolate data changes for review, tests, cleanup, and proposal workflows.
- Write proposals
  URL: https://synapsor.ai/docs/write-proposals
  Summary: Write proposals stage risky agent writes for human or policy approval.
- Settlement policies
  URL: https://synapsor.ai/docs/settlement-policies
  Summary: Policy-driven proposal settlement approves, commits, merges, or holds Synapsor-native writes; external targets are approved for trusted writeback.
- Replay
  URL: https://synapsor.ai/docs/replay
  Summary: Replay reruns a captured agent workflow against the original or current context.
- RBAC and policies
  URL: https://synapsor.ai/docs/rbac-policies
  Summary: RBAC, security policies, and redaction policies constrain who can create, invoke, approve, commit, read, and inspect agent workflows.
- Hybrid search
  URL: https://synapsor.ai/docs/hybrid-search
  Summary: Hybrid search combines lexical and vector retrieval for policy, docs, and memory-backed agents.
- Projects
  URL: https://synapsor.ai/docs/projects
  Summary: Projects are the billing, quota, usage, and audit boundary in Synapsor Cloud.
- Databases
  URL: https://synapsor.ai/docs/databases
  Summary: Hosted databases map to runtime branches in the current V2 single-node architecture.
- API keys
  URL: https://synapsor.ai/docs/api-keys
  Summary: API keys authenticate database and control-plane requests.
- Regions
  URL: https://synapsor.ai/docs/regions
  Summary: Hosted V2 controlled beta currently runs in one operator-selected region while the control plane prepares for future regional placement.
- Quotas
  URL: https://synapsor.ai/docs/quotas
  Summary: Quotas enforce plan limits for projects, databases, external sources, storage, branches, agent capability invocations, embeddings, and backups.
- Backups
  URL: https://synapsor.ai/docs/backups
  Summary: Backups copy runtime data into encrypted backup objects with manifest-style status in the control plane.
- PITR
  URL: https://synapsor.ai/docs/pitr
  Summary: Point-in-time recovery remains operator-controlled during V2 controlled beta.
- Billing
  URL: https://synapsor.ai/docs/billing
  Summary: Billing tracks plan state, checkout, portal access, usage, and spend caps.
- Usage limits
  URL: https://synapsor.ai/docs/usage-limits
  Summary: Usage limits protect hosted reliability and control cost.
- Error codes
  URL: https://synapsor.ai/docs/error-codes
  Summary: Synapsor APIs return structured errors so SDKs and dashboards can react consistently.
- REST API
  URL: https://synapsor.ai/docs/rest-api
  Summary: The REST API exposes hosted control-plane, SQL, agent, evidence, proposal, and backup workflows.
- SQL API
  URL: https://synapsor.ai/docs/sql-api
  Summary: The SQL API executes SQL against the database branch associated with the API key.
- Python SDK
  URL: https://synapsor.ai/docs/python-sdk
  Summary: The Python SDK wraps hosted SQL, sessions, capabilities, proposals, and backups.
- Node SDK
  URL: https://synapsor.ai/docs/node-sdk
  Summary: The Node SDK wraps hosted SQL, sessions, capabilities, proposals, and backups for JavaScript apps.
- CLI status
  URL: https://synapsor.ai/docs/cli-status
  Summary: The Synapsor CLI is available in the Node package as a controlled-beta command-line surface for hosted SQL and agent workflows.
- CLI quickstart
  URL: https://synapsor.ai/docs/cli-quickstart
  Summary: Install the Synapsor CLI, configure an API key, run SQL, invoke a capability, inspect evidence, preview a proposal, and replay a run.
- Browser Console
  URL: https://synapsor.ai/docs/browser-console
  Summary: The signed-in browser Console runs scoped Synapsor SQL/API commands from the dashboard without exposing server shell access.
- Expense Guard lab
  URL: https://synapsor.ai/docs/expense-guard-lab
  Summary: A demo-specific comparison of Postgres app glue versus Synapsor durable run state.
- Contract-to-Cash lab
  URL: https://synapsor.ai/docs/contract-to-cash-lab
  Summary: A demo-specific comparison of contract billing logic with app-owned glue versus Synapsor durable run state.
- OpenAPI spec
  URL: https://synapsor.ai/docs/openapi-spec
  Summary: The OpenAPI spec is public and machine-readable for SDK generation, docs, and contract tests.

## Documentation links

### Start here

Understand database MCP commit safety and create one reviewable agent database change.

- Database MCP commit safety
  URL: https://synapsor.ai/docs/mcp
- MCP quickstart
  URL: https://synapsor.ai/docs/mcp-quickstart
- Overview
  URL: https://synapsor.ai/docs/start-here
- Quickstart
  URL: https://synapsor.ai/docs/quickstart
- Existing Postgres/MySQL
  URL: https://synapsor.ai/docs/existing-databases
- Write proposals
  URL: https://synapsor.ai/docs/existing-db-write-proposals
- Open-source runner
  URL: https://synapsor.ai/docs/open-source-runner

### Database MCP

Expose semantic MCP tools, bind trusted context, create proposals, and commit through a guarded runner.

- MCP mental model
  URL: https://synapsor.ai/docs/mcp
- MCP quickstart
  URL: https://synapsor.ai/docs/mcp-quickstart
- Local runtime
  URL: https://synapsor.ai/docs/mcp-local-runtime
- Cloud mode
  URL: https://synapsor.ai/docs/mcp-cloud-mode
- Semantic tools
  URL: https://synapsor.ai/docs/mcp-semantic-tools
- Trusted context
  URL: https://synapsor.ai/docs/mcp-trusted-context
- Read-only and shadow mode
  URL: https://synapsor.ai/docs/mcp-shadow-mode
- Write proposals
  URL: https://synapsor.ai/docs/mcp-write-proposals
- Trusted runner and conflict detection
  URL: https://synapsor.ai/docs/mcp-trusted-runner
- Stale-row conflicts
  URL: https://synapsor.ai/docs/mcp-conflict-detection
- Replay
  URL: https://synapsor.ai/docs/mcp-replay
- Static MCP risk review
  URL: https://synapsor.ai/docs/mcp-audit
- Security boundary
  URL: https://synapsor.ai/docs/mcp-security-boundary
- Client setup
  URL: https://synapsor.ai/docs/mcp-client-setup
- Agent framework adapters
  URL: https://synapsor.ai/docs/agent-adapters
- Open-source runner
  URL: https://synapsor.ai/docs/open-source-runner

### Existing database change control

Govern reads, create row diffs, approve proposals, and apply conflict-checked writeback.

- Source mappings and least-privilege reads
  URL: https://synapsor.ai/docs/existing-db-ui-setup
- Trusted session binding
  URL: https://synapsor.ai/docs/hidden-session-bindings
- Evidence bundles
  URL: https://synapsor.ai/docs/evidence-bundles
- Evidence and query audit
  URL: https://synapsor.ai/docs/find-evidence-later
- Review branches and row diffs
  URL: https://synapsor.ai/docs/existing-db-write-proposals
- Approval/policy
  URL: https://synapsor.ai/docs/settlement-policies
- Trusted writeback
  URL: https://synapsor.ai/docs/open-source-runner
- Conflict handling and idempotency
  URL: https://synapsor.ai/docs/existing-db-write-proposals
- Replay
  URL: https://synapsor.ai/docs/replay
- Security model
  URL: https://synapsor.ai/docs/existing-db-security
- Agent Activity
  URL: https://synapsor.ai/docs/agent-activity
- Connect Postgres
  URL: https://synapsor.ai/docs/connect-postgres
- Connect MySQL
  URL: https://synapsor.ai/docs/connect-mysql

### Framework integrations

Use Synapsor beside your ORM and agent framework without exposing raw SQL to the model.

- Agent framework adapters
  URL: https://synapsor.ai/docs/agent-adapters
- Prisma with Synapsor
  URL: https://synapsor.ai/docs/prisma-postgres-synapsor
- Drizzle with Synapsor
  URL: https://synapsor.ai/docs/drizzle-postgres-synapsor
- SQLAlchemy with Synapsor
  URL: https://synapsor.ai/docs/sqlalchemy-postgres-synapsor
- Django with Synapsor
  URL: https://synapsor.ai/docs/django-postgres-synapsor
- Rails with Synapsor
  URL: https://synapsor.ai/docs/rails-postgres-synapsor
- Workflow examples
  URL: https://synapsor.ai/docs/workflow-examples
- Observability and traces
  URL: https://synapsor.ai/docs/observability-traces

### Synapsor-native — advanced

Use real Synapsor branch, settlement, memory, search, and workflow state when data lives in Synapsor.

- Branching modes
  URL: https://synapsor.ai/docs/branching-modes
- Native branches
  URL: https://synapsor.ai/docs/branches
- Settlement policies
  URL: https://synapsor.ai/docs/settlement-policies
- Native workflows
  URL: https://synapsor.ai/docs/agent-workflows
- Agent contexts
  URL: https://synapsor.ai/docs/agent-contexts
- Agent capabilities
  URL: https://synapsor.ai/docs/agent-capabilities
- Capability plans
  URL: https://synapsor.ai/docs/capability-plans
- Auto-branching
  URL: https://synapsor.ai/docs/auto-branching
- Write proposals
  URL: https://synapsor.ai/docs/write-proposals
- Governed memory
  URL: https://synapsor.ai/docs/governed-memory
- Hybrid search
  URL: https://synapsor.ai/docs/hybrid-search
- Agent evals and regression replay
  URL: https://synapsor.ai/docs/agent-evals
- Agent time travel
  URL: https://synapsor.ai/docs/agent-time-travel

### Reference

REST, SQL, SDKs, CLI, system views, and generated API contracts.

- What is Synapsor?
  URL: https://synapsor.ai/docs/what-is-synapsor
- REST API
  URL: https://synapsor.ai/docs/rest-api
- SQL API
  URL: https://synapsor.ai/docs/sql-api
- SQL extensions
  URL: https://synapsor.ai/docs/sql-extensions
- Python SDK
  URL: https://synapsor.ai/docs/python-sdk
- Node SDK
  URL: https://synapsor.ai/docs/node-sdk
- CLI status
  URL: https://synapsor.ai/docs/cli-status
- CLI quickstart
  URL: https://synapsor.ai/docs/cli-quickstart
- Browser Console
  URL: https://synapsor.ai/docs/browser-console
- OpenAPI spec
  URL: https://synapsor.ai/docs/openapi-spec
- System views
  URL: https://synapsor.ai/docs/system-views
- Agent catalog and introspection
  URL: https://synapsor.ai/docs/agent-catalog-introspection
- RBAC and policies
  URL: https://synapsor.ai/docs/rbac-policies
- Token budgets and evidence lookup ids
  URL: https://synapsor.ai/docs/token-budgets-evidence-handles
- Agent syntax glossary
  URL: https://synapsor.ai/docs/agent-syntax-glossary
- Value sources and lookup ids
  URL: https://synapsor.ai/docs/value-sources-and-handles
- Table constraints
  URL: https://synapsor.ai/docs/table-constraints

### Operations and beta status

Controlled-beta limits, production-oriented architecture, cloud operations, labs, and private previews.

- Known limitations
  URL: https://synapsor.ai/docs/known-limitations
- Production-oriented architecture
  URL: https://synapsor.ai/docs/production-single-node-architecture
- Existing DB production architecture
  URL: https://synapsor.ai/docs/existing-db-production-architecture
- Security
  URL: https://synapsor.ai/security
- Storage profiles
  URL: https://synapsor.ai/docs/storage-profiles
- Projects
  URL: https://synapsor.ai/docs/projects
- Databases
  URL: https://synapsor.ai/docs/databases
- Create a project
  URL: https://synapsor.ai/docs/create-project
- Create a database
  URL: https://synapsor.ai/docs/create-database
- API keys
  URL: https://synapsor.ai/docs/api-keys
- Regions
  URL: https://synapsor.ai/docs/regions
- Quotas
  URL: https://synapsor.ai/docs/quotas
- Backups
  URL: https://synapsor.ai/docs/backups
- PITR
  URL: https://synapsor.ai/docs/pitr
- Billing
  URL: https://synapsor.ai/docs/billing
- Billing and cancellation
  URL: https://synapsor.ai/docs/billing-and-cancellation
- Free vs Builder
  URL: https://synapsor.ai/docs/free-vs-builder
- Usage limits
  URL: https://synapsor.ai/docs/usage-limits
- Error codes
  URL: https://synapsor.ai/docs/error-codes
- Existing DB modes
  URL: https://synapsor.ai/docs/external-db-modes
- Existing DB 15-minute quickstart
  URL: https://synapsor.ai/docs/existing-db-quickstart
- Existing DB live demo
  URL: https://synapsor.ai/docs/existing-db-live-demo
- AWS RDS and Aurora setup
  URL: https://synapsor.ai/docs/aws-rds-existing-db
- CDC roadmap
  URL: https://synapsor.ai/docs/existing-db-cdc-roadmap
- External DB CDC private preview
  URL: https://synapsor.ai/docs/external-db-cdc
- CDC glossary
  URL: https://synapsor.ai/docs/external-db-cdc-glossary
- Expense Guard lab
  URL: https://synapsor.ai/docs/expense-guard-lab
- Contract-to-Cash lab
  URL: https://synapsor.ai/docs/contract-to-cash-lab
- Examples
  URL: https://synapsor.ai/examples