Local Development
Install CentraKit, start the local Supabase stack and the apps with or without Portless, and sign in with the seeded personas.
Dashboard
What the organization dashboard shows, including metric cards, the operations pulse, capacity allocation, recent activity and the people reminders for absences, celebrations and HR deadlines.
Local Development
Install CentraKit, start the local Supabase stack and the apps with or without Portless, and sign in with the seeded personas.
Dashboard
What the organization dashboard shows, including metric cards, the operations pulse, capacity allocation, recent activity and the people reminders for absences, celebrations and HR deadlines.
How the five CentraKit apps deploy as services in one Vercel project, including domains, routing rewrites and the 11 crons in vercel.json.
CentraKit is deployed as five independently built services in one Vercel project rooted at the
repository root. The root vercel.json owns service definitions, public routing, and cron schedules.
Shared packages continue to build through Turborepo.
Each service installs with pnpm install --filter <app>... and builds with
turbo run build --filter=<app>. Per-service ignoreCommand runs pinned turbo-ignore (with
--turbo-version so the pnpm catalog pin does not break version inference) so unaffected apps skip
the build (for example an api-only change rebuilds api, and docs when OpenAPI or docs/**
inputs change, but not saas / marketing / showcase).
Never list .git in .vercelignore. Selective skips and Turbo remote cache need git metadata on the
build machine. Keep ignoring agent trees, tests, apps/cli, and other non-runtime paths instead.
saas and api both enable the Workflow SDK. Their Turbo build outputs include
app/.well-known/workflow/**, and each build command sets a distinct WORKFLOW_QUEUE_NAMESPACE
so the shared deployment does not register duplicate __wkf_workflow_* queue consumers. Production
builds use saas and api; every other environment appends preview (saaspreview,
apipreview).
| Service | App root | Production domain | Preview domain (develop) | Notes |
|---|---|---|---|---|
saas | apps/saas | app.centrakit.com | app.centrakit.dev | Signed-in SaaS app. |
api | apps/api | api.centrakit.com | api.centrakit.dev | REST API, MCP server, OAuth and crons. |
docs | apps/docs | docs.centrakit.com | docs.centrakit.dev | Fumadocs site generated from root docs/. |
marketing | apps/marketing | sample.centrakit.com | sample.centrakit.dev | Public marketing template. |
showcase | apps/showcase | centrakit.com and www.centrakit.com | centrakit.dev and www.centrakit.dev | Template showcase. |
Only develop and main deploy. git.deploymentEnabled in vercel.json turns deployments off for every other branch, including changeset-release/*.
Use the single project's Vercel-managed environment for all services. Shared values such as the
Supabase connection, Sentry, and one public origin (NEXT_PUBLIC_SITE_URL or the Vercel production domain) are configured once. AI Gateway uses OIDC (VERCEL_OIDC_TOKEN).
Run pnpm env:pull from the repository root to refresh .env.local (development) and
.env.production.local (production).
Turborepo filters build-time variables through each app's turbo.json; add every build-time secret there when an app needs it during build, typecheck, or another task.
Project environment variables are visible to every service. Vercel Services do not provide a general per-service environment allowlist, so treat server-only credentials as project-wide secrets. Use a separate Vercel project when a surface requires an independent credential or deployment-protection boundary.
The first-party project runs Vercel Functions in fra1 (Frankfurt) to match its Supabase
eu-central-1 region. Keep the function and database regions aligned. Static assets remain
globally distributed by Vercel's CDN.
The rewrites in vercel.json run in order. Path rules come first and send these paths to the API
service on any host:
/api/v1/:path*, /api/mcp/:path* and /.well-known/oauth-protected-resource./portal/calendars/:token and /portal/files/:token, which map to the public calendar and file
routes under /api/v1/public/.Host rules then pick the service for each production and preview domain in the table above. The final catch-all sends any other host, including generated deployment URLs, to SaaS. Marketing, docs, and showcase previews therefore need their preview domain for browser checks.
vercel.json defines 11 crons. Vercel calls each path with GET on the production deployment, and
the /api/v1/:path* rewrite routes all of them to the API service. Schedules are in UTC.
| Path | Schedule | Job |
|---|---|---|
/api/v1/internal/google-calendar-sync | */5 * * * * | Syncs connected Google calendars into the agenda. |
/api/v1/workflows/audit-log/retention | 17 2 * * * | Starts the audit log retention workflow. |
/api/v1/workflows/scheduler/watchdog | */5 * * * * | Checks that the workflow scheduler is running and starts it when it is not. |
/api/v1/internal/channel-webhook-jobs | * * * * * | Processes queued inbound channel webhooks for the inbox. |
/api/v1/internal/webhook-deliveries | * * * * * | Sends due outbound webhook deliveries. |
/api/v1/internal/files/upload-reconciliation | */15 * * * * | Expires stale file uploads and removes their Storage objects. |
/api/v1/internal/files/zip-exports | * * * * * | Builds requested ZIP exports of files. |
/api/v1/internal/people/daily | 7 6 * * * | People reminders, time-off accrual, sick leave follow-up, forgotten timers and attendance, and expired candidate cleanup. |
/api/v1/internal/approvals/sweep | */10 * * * * | Escalates and expires pending approval requests and sends the matching notifications. |
/api/v1/internal/inventory/signals | * * * * * | Publishes inventory level events such as low stock to workflows. |
/api/v1/internal/commerce/daily | 17 6 * * * | Publishes overdue purchase order and promotion events. See Workflows. |
Each cron route reports to a Sentry Cron monitor through withMonitor. Set CRON_SECRET (at least
32 characters) in the project environment. Without it, cron routes answer with a
CRON_UNAVAILABLE problem response instead of running. Keep the /api/v1/:path* rewrite ahead of
the SaaS catch-all.
apps/api/public/openapi.json.packages/api-client.Regenerate committed API artifacts after route handler or schema documentation changes.
Last updated on
Local Development
Install CentraKit, start the local Supabase stack and the apps with or without Portless, and sign in with the seeded personas.
Dashboard
What the organization dashboard shows, including metric cards, the operations pulse, capacity allocation, recent activity and the people reminders for absences, celebrations and HR deadlines.