Deploy and Host Nakatomi CRM on Railway

Nakatomi is a headless, agent-native CRM (v1.0.7). 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

Variable	Required	Notes
`SECRET_KEY`	yes	Generated by template
`DATABASE_URL`	yes	Linked from Postgres
`ENVIRONMENT`	yes	`production`
`PUBLIC_BASE_URL`	recommended	Set to your Railway domain after first deploy
`BOOTSTRAP_TOKEN`	recommended	Protect first-run `/` claim if the URL is public before you open it
`API_KEY_RATE_LIMIT_PER_MINUTE`	optional	e.g. `120` in production
`AUTH_RATE_LIMIT_PER_MINUTE`	optional	e.g. `30` for OAuth/login/bootstrap
`OTEL_` / `SSO_`	no	Optional observability and human SSO

After deploy, open /health — expect "version":"1.0.7". First visit to / shows the branded welcome flow (workspace + API key).

Agent MCP (important)

Create a workspace API key: POST /workspace/api-keys (role owner/admin, scopes *).
Point your MCP client at https://YOUR-DOMAIN.up.railway.app/mcp (not the site root).
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