Deploy NakatomiCRM

Deploy and Host Nakatomi CRM on Railway

Nakatomi is a headless, agent-native CRM (v1.0). REST + MCP + A2A + ACP on Postgres — built for Claude, ChatGPT, Cursor, and custom agent swarms.

About Hosting

This template provisions:

• nakatomi — FastAPI app (Dockerfile), Alembic migrations on boot, healthcheck at /health
• Postgres — managed database with DATABASE_URL linked automatically
• Volume at /app/data for local file storage
• Auto-generated SECRET_KEY and production defaults

Public URL: https://railway.com/deploy/nakatomicrm

Why Deploy

• One-click agent CRM with scoped API keys and HITL approvals
• MCP tools at /mcp (including custom fields / custom objects)
• Multi-CRM importers, jobs, policies, forensics
• Optional OpenTelemetry and Google/GitHub SSO via env vars
• Protocol stability SLA (90-day sunset for breaking changes)

Common Use Cases

• Give coding agents a structured CRM spine (contacts, companies, deals, leads)
• Multi-agent GTM workflows over A2A tasks + ACP context packs
• Self-hosted alternative to SaaS CRMs when agents are the primary client
• Workspace-tunable schema via custom fields and custom objects

Dependencies for Nakatomi CRM Hosting

• Railway account (Hobby or higher recommended for always-on)
• Optional: S3-compatible bucket if you switch STORAGE_BACKEND=s3
• Optional: OIDC apps for Google/GitHub SSO

Deployment Dependencies

After deploy, open /health — expect "version":"1.0.0".

Agent MCP (important)

1. Create a workspace API key: POST /workspace/api-keys (role owner/admin, scopes *).
2. Point your MCP client at https://YOUR-DOMAIN.up.railway.app/mcp (not the site root).
3. Header: Authorization: Bearer nk_…

Bare /mcp and /mcp/ both work. Do not use the welcome URL alone as the MCP endpoint.

Source: github.com/mrdulasolutions/NakatomiCRM