Supported languages and stacks
Tokay analyzes the project files to choose the runtime, framework, and start command, so most applications do not need platform specific build configuration. This page describes the environments we have verified and what to do when Tokay cannot identify a runnable Service.
Last updated
AI agent? Start with llms.txt.
Supported runtimes
Tokay supports Node.js, Bun, Python, Go, Ruby, Rust, PHP, Bash/POSIX shell, and static HTML.
Version requirements in the project are respected. Examples include a go.mod toolchain line, a Rust toolchain file, or a PHP version requirement in Composer. When the project does not pin a version, Tokay chooses a current supported version.
Verified frameworks
The following frameworks have been tested end to end. An unlisted framework can still work when it uses a supported runtime and a normal build or start command, and plain scripts work in every supported language.
- Node.js and Bun. Express, Next.js, Nuxt, SvelteKit, Astro, Remix, Koa, Fastify, Hapi, NestJS, Hono, Restify, SolidStart, and Qwik.
- Python. Django, FastAPI, Flask, Starlette, Litestar, Quart, Falcon, Bottle, Pyramid, and Streamlit.
- Ruby. Rails, Sinatra, Roda, Hanami, Grape, Padrino, and Cuba.
- PHP. Laravel, Symfony, Slim, Lumen, CodeIgniter, and CakePHP.
- Go. net/http, Fiber, Gin, Echo, Chi, Gorilla/mux, and Beego.
- Rust. Axum, Actix-web, Rocket, Warp, Poem, Tide, and Salvo.
Static site generators
A static site builds during deployment and is served as a web app with HTTPS and a URL like any other.
A site moving from Netlify or Cloudflare Pages keeps the _redirects and _headers files in its output folder, and Tokay applies the rules that name an exact path. That covers redirecting /old-page to another page or to an https:// address, serving one of the site's files at another path, showing a page for a missing one, and adding headers to one path or to every path with /*. A file at a path still wins over a rule for it. Lines that use wildcards or :placeholders are skipped, and the deploy lists them in its warnings so you can rewrite them as exact paths.
- Hugo, Astro, Eleventy, Gatsby, Docusaurus, VitePress, and Next.js (static export).
Database migration tools
When the code uses one of these tools, Tokay runs the migration as part of the deploy. Database migrations describes the rehearsal, snapshot, and approval safety around every run.
- Node.js. Prisma, Drizzle, Sequelize, TypeORM, MikroORM, Knex, and Graphile Migrate.
- Python. Django, Alembic, and Aerich.
- Ruby. ActiveRecord.
- PHP. Eloquent.
- Go. golang-migrate and Atlas.
- Rust. SQLx and Diesel.
Package managers
Tokay detects the package manager from the project's manifest and lockfile and installs dependencies with it.
When Tokay chooses dependency versions itself, as it does for a project with no lockfile, it waits seven days before it uses a new release with npm, Bun, uv, and pip, so a bad release can be caught before it reaches your app. A lockfile installs exactly as written. An exact version in your manifest is honored on its first day, so pin a new release exactly when you need it sooner, such as a security fix. Activity names each dependency the wait held back.
- Node.js and Bun. npm, pnpm, Yarn, and Bun.
- Python. pip, uv, Poetry, PDM, and Pipenv.
- Ruby. Bundler.
- PHP. Composer.
- Go. go modules.
- Rust. Cargo.
System tools are part of the runtime
Some applications call operating system packages to generate PDFs, process images, or run a headless browser. Tokay detects those calls and includes the required tools in the Service environment when supported.
Bash scripts can run on a schedule, continuously as background workers, or once per HTTP request as functions. No dependency manifest or executable bit is required. Functions receive the request body on stdin and return stdout as the response. Shell source contract describes request metadata and execution behavior.
The common toolbox includes curl, jq, Mike Farah's Go yq v4, PostgreSQL clients, MySQL-compatible clients, Redis CLI, and common archive and transfer tools. Mongo tools are added when the code needs them.
Make an unusual project detectable
Make sure the code includes a clear entry point and uses a supported runtime. If Tokay does not find a runnable Service, add or clarify an entry point such as server.js, app.py, script.sh, or index.html, then push or analyze the code again.
See How Tokay sets up your app for the full detection and review process.