Run a maintenance command on a deployed app
Run a one-off command in the application's real environment without opening SSH access or reconstructing its configuration in a shell. Tokay executes the task against the current deployed Service and records who ran it, its output, and its exit state.
Last updated
The command sees what the app sees
You do not need to copy secrets or database credentials into a separate maintenance environment. Give Tokay a command such as python manage.py clearsessions or node scripts/backfill.js, and the task receives the deployed app's environment variables, secrets, database access, and persistent storage.
The command uses the current deployed code, so operational work cannot accidentally run against an unshipped local version.
Every task leaves an audit record
Tokay preserves the command, output, exit state, time, and identity that ran it. A late night backfill or cleanup has a durable answer to what ran and what happened.
This removes the need to distribute shell keys, expose an SSH port, or reconstruct activity from terminal history.
Schema migrations use the deployment workflow
Database schema changes need rehearsal, snapshots, and approval boundaries rather than a general maintenance task. Use deploy database migrations safely for those changes. Tasks cover operational commands around the deployed application.
Your AI agent can perform recorded maintenance
A coding agent like Claude Code or Codex can run a task through Tokay's GraphQL API, poll its state, and read the recorded output. The action is attributed to the agent's own identity and credential rather than a shared shell login.
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.