Under the Hood

From code to URL
in six steps.

You run telbase deploy. Here is everything that happens between that command and your app going live β€” the analysis, the routing decisions, the provisioning, the wiring. Every step, explained.

1
Analyze
2
Route
3
Provision
4
Migrate
5
Deploy
6
Verify
Start FreeSee the Product
Step 1

Your code tells us everything.

Telbase scans your project files to detect your framework, database ORM, SQL dialect, and API patterns. Your code is your configuration β€” nothing to write, nothing to declare.

πŸ“„package.json
πŸ“„next.config.js
πŸ“prisma/
πŸ“„schema.prisma
πŸ“src/
πŸ“app/
πŸ“„page.tsx
πŸ“„layout.tsx
πŸ“api/
πŸ“„route.ts
πŸ“„.env.example
Framework
from package.json
Next.js 14 (App Router)
ORM
from prisma/schema.prisma
Prisma
Database Dialect
from prisma/schema.prisma
PostgreSQL
Environment Requirements
from .env.example
DATABASE_URL (required)
Worker Type
from requirements.txt + worker_main.py
Daemon (APScheduler)

We read your configuration files the same way a developer would β€” package.json for framework and dependencies, schema files for ORM and dialect, directory structure for service boundaries. No .telbase.yml. No build configuration. Your existing code is the only input.

Step 2

Telbase picks the right infrastructure for each layer.

Based on what we detected, Telbase routes each layer of your application to the optimal infrastructure β€” the same choices a senior engineer would make, without you needing to know the options exist.

Your Code
Next.js + Prisma + PostgreSQL
Telbase Routing Engine
Analyzes framework, ORM, and dialect
</​>
Edge Hosting
Global CDN, server-side rendering, instant cache invalidation. Optimized for frontend frameworks.
Next.js, Remix, SvelteKit, Astro, Vite
βš™
Container Compute
Auto-scaling containers with persistent compute. Optimized for backend APIs and services.
Django, FastAPI, Go, Express, Docker
β—«
Managed Database
Serverless, scale-to-zero, automatic backups. Provisioned and connected automatically.
PostgreSQL, SQLite

Telbase deploys to enterprise-grade cloud providers including Vercel, Google Cloud, and Neon. You don’t need accounts with any of them β€” Telbase manages the infrastructure on your behalf.

Step 3

Everything is provisioned and wired automatically.

Once routing decisions are made, Telbase provisions the infrastructure you need β€” database instances, environment variables, SSL certificates, and subdomain routing. All in one pass.

βœ“
Database instance
A managed PostgreSQL or SQLite database is created for your project. Isolated per project, serverless, scale-to-zero when idle.
βœ“
Connection strings injected
DATABASE_URL and any required connection variables are set as environment variables on your compute provider. No copy-pasting from dashboards.
βœ“
SSL certificates
HTTPS is configured automatically. Your app is served over TLS from the first request.
βœ“
Subdomain routing
Your app gets a URL at your-app.telbase.ai. Multi-service apps get separate subdomains β€” project.telbase.ai for the frontend, project-api.telbase.ai for the backend.
βœ“
Environment variable wiring
API URLs, CORS origins, and service discovery variables are detected from your code patterns and configured between services.
Step 4

Database migrations run on deploy.

Telbase detects your ORM and runs the correct migration command automatically. No SSH sessions. No manual migration steps. Schema changes are applied before your new code goes live.

Scanning for ORM...→ Detected: Prisma (from prisma/schema.prisma)→ Migration command: npx prisma migrate deploy→ Running against: DATABASE_URL (managed PostgreSQL)→ Migrations applied: 3 pending → done
ORMMigration CommandDialects
Prismanpx prisma migrate deployPostgreSQL, SQLite
Drizzlenpx drizzle-kit pushPostgreSQL, SQLite
Django ORMpython manage.py migratePostgreSQL
Alembicalembic upgrade headPostgreSQL
GORM / EntAuto-migrate at runtimePostgreSQL

Migrations are the step most platforms skip. They expect you to SSH in or run a separate command. Telbase treats migrations as part of the deploy β€” because a deploy is new code plus the schema it requires.

Steps 5 & 6

Build, deploy, verify.

Your code is built, deployed to production, and health-checked. The URL is live when the health check passes.

Build
Code is compiled and optimized.
Built using the optimal pipeline for your framework. Frontend frameworks get an optimized SSR build. Backend APIs are containerized automatically. Static sites can skip the cloud build entirely β€” Telbase builds locally and uploads the output.
20–40s
Deploy
Traffic routes to the new version.
The built artifact is deployed as a new revision. Traffic is routed to the new version automatically. Instant rollback is available if anything goes wrong.
10–20s
Verify
Health check confirms it’s live.
Telbase checks that your application is responding on its URL. If the health check fails, the deploy is marked as failed and you get structured error diagnostics β€” not a blank page and a mystery.
5–10s
When Things Break

Failures are diagnosed, not just reported.

When a deploy fails, Telbase applies three diagnosis layers: 97 error patterns, 11 classification cross-reference rules, and an AI agent that reads your source code β€” returning the root cause down to the file and line.

Other Platforms
Error: connect ECONNREFUSED 127.0.0.1:5432 at TCPConnectWrap.afterConnect at Object.onceWrapper (events.js:520:26) at TCPConnectWrap.emit (events.js:400:28)
Telbase
{ "diagnosis": "src/server.ts imports @hono/node-server but it is not in package.json dependencies", "confidence": 0.95, "category": "missing_dependency", "fixes": [{ "type": "dependency", "description": "npm install @hono/node-server", "autoFixable": true }], "redeployCommand": "telbase deploy" }
3
diagnosis layers
97+
error patterns
~95%
first-try fix rate
1
retry to success
Compatibility

Frameworks, ORMs, and databases.

Everything Telbase detects and deploys automatically.

Frameworks
Next.jsApp Router & Pages
Remix
SvelteKit
Astro
Angular
ViteReact, Vue, Svelte, Solid
Full-StackVite + Express/Hono/Fastify
Express
NestJS
FastAPI
Django
Flask
Gonet/http, Gin, Echo, Fiber
Node.jsGeneric with start script
DockerAny language
Static HTML
ORMs
PrismaPostgreSQL, SQLite
DrizzlePostgreSQL, SQLite
SQLAlchemyPostgreSQL
Django ORMPostgreSQL
GORMPostgreSQL
EntPostgreSQL
Databases
PostgreSQLManaged, serverless
SQLiteManaged, distributed
Open Standard

Works from any AI coding tool.

Telbase uses MCP β€” the Model Context Protocol β€” for AI agent integration. 41 tools, 14 documentation resources, and 3 guided prompts β€” all returning structured JSON.

Claude CodeCursorWindsurfVS Code + CopilotGitHub Copilot CLI
Deploy & Monitoring
6 tools
deploy, get_deploy_status, +4 more
Project Management
4 tools
list_projects, get_project, +2 more
Service Control
5 tools
check_app_health, restart_service, +3 more
Rollback
2 tools
rollback_deploy, list_rollback_targets
Environment Variables
3 tools
set_env_vars, list_env_vars, +1 more
Database
2 tools
get_database_info, enable_database_extension
Custom Domains
4 tools
add_custom_domain, verify_custom_domain, +2 more
Scheduled Jobs
5 tools
get_job_executions, run_scheduled_job, +3 more
Storage
2 tools
get_storage_info, get_storage_credentials
GitHub
3 tools
get_github_status, connect_github, +1 more
Team & Organization
4 tools
list_team, invite_member, +2 more
Account
1 tool
get_account_status
// Every response is structured JSON // Your AI agent parses it and acts { "status": "live", "url": "https://my-app.telbase.ai", "usage": { "deploys_used": 7, "deploys_limit": 30 }, "next_steps": [ "Add a custom domain", "Set environment variables" ] }

Now you know how it works. Try it.

One command. Enterprise infrastructure. Free tier. No credit card.

$ telbase deploy
Start Free β†’