Skip to main content
Three ways to run Teable — pick by what you need:
Already running Teable? Upgrading an existing deployment to the full-featured platform is covered step by step by the migration guide in the deployment repository: the runtime plane installs next to your existing Teable, and your data stays in place.

Let an AI agent deploy it

The deployment repository is written to be driven by AI agents. Point your agent harness (Claude Code, Codex, …) at teableio/teable-deployment, tell it which environment you’re deploying to, and it can take the deployment end to end. Prepare three things:
  1. A domain — everything derives from one base domain, e.g. teable.example.com.
  2. A DNS token — an API token for the platform hosting your DNS (Cloudflare, Route 53, …), so DNS records and TLS certificates can be set up automatically. Scope it to that one zone.
  3. Access to the deployment target:
That’s all it takes — the repository’s guides, doctor scripts, and version manifests carry the agent through the rest.
Last modified on July 17, 2026