Deploy a monorepo with multiple services
Deploy the application represented by your monorepo without re-entering every root, start command, and dependency as platform configuration. Tokay reads the committed code, identifies the deployable processes, and shows you how the repository maps to production.
Last updated
The repo defines the Services
You can review a proposed deployment instead of creating each Service by hand. Connect GitHub or push the repository, and Tokay identifies web apps, workers, scheduled jobs, and webhooks along with their service roots, entry points, environment variables, and database needs.
Confirm the processes you want to run, and Tokay deploys them into one Project. Each Service keeps its own URL, logs, settings, deployment history, and lifecycle.
Related processes stay related
Tokay preserves the relationships already present in the code, so the frontend, API, workers, and jobs do not need separate hosting plans. Services in the same Project share databases, secrets, and private networking on the Workspace's dedicated virtual machine.
A frontend and backend that build and run as one application stay in one web Service. Processes with independent lifecycles get separate Services.
Updates stay focused on changed code
A small change does not have to rebuild the entire monorepo. Tokay determines which Services are affected by a push and skips those whose code did not change.
The unchanged Services keep running and continue to use the same Project resources while the updated Services deploy.
Your AI agent can work from detected candidates
A coding agent like Claude Code or Codex can deploy the monorepo without guessing roots and start commands. Through Tokay's GraphQL API, it can submit the repository, inspect the detected Service candidates, confirm the intended set, provide missing secrets, deploy the Project, and verify each public endpoint.
Point your agent to app.tokay.io/llms.txt for the deployment protocol.
Tokay has a very generous free tier with no credit card. Get started.