Plans & Usage

How Telbase counts resources against your plan — and what happens when you need more.

Quick Reference

ResourceWhat It IsScopeOverages
WebsitesStatic sites (Vite, Astro, HTML)Per orgUnlimited on paid
AppsFull-stack projects (Next.js, Django, etc.)Per org20 credits/mo ($2)
DeploysEvery deploy attempt (success or failure)Monthly, org1 credit ($0.10)
DatabasesSQLite or PostgreSQL, counted equallyPer org15 credits/mo ($1.50)
Custom DomainsNon-*.telbase.ai domains (Free: 0, Starter: 1, Builder: 5, Pro: unlimited)Per orgNot credit-expandable
Scheduled JobsCron jobs via Cloud SchedulerPer org20 credits/mo ($2)
File StorageR2 object storage (Free: 0, Starter: 1 GB, Builder: 5 GB, Pro: 25 GB)Per projectIncluded in plan
Always OnKeep one GCP instance warm (eliminates cold starts)Per service100 credits/mo ($10), Pro includes 1
Team MembersCollaborators in your organization (Free: 1, Paid: unlimited)Per org
Credits$1 = 10 credits, 12-month expiryPer org

Websites

A website is any project built with a static framework: Vite, Astro, or plain HTML (no package.json).

Apps

An app is any project using a framework other than Vite, Astro, or static HTML. This includes:

Framework-based, not database-based
Classification depends on your framework, not whether you have a database. A Next.js project without a database still counts as an app. A Vite project that connects to an external API still counts as a website.

Plan limits:

Deploys

A deploy is any deploy attempt — whether it succeeds, fails, or is cancelled. All types count:

Failed deploys count
Every attempt counts against your monthly limit, including failures. This prevents gaming the system by retrying indefinitely. If a build fails, fix the issue before redeploying.

Multi-service projects: each service counts as 1 deploy. A 3-service monorepo uses 3 deploys per push.

Deploy limits reset on the 1st of each month (UTC):

Databases

SQLite and PostgreSQL databases count equally — 1 database = 1 against your limit regardless of type. The count is org-wide across all projects.

See Databases for provisioning, migrations, backups, and extensions.

Multi-Service Projects

When you deploy a monorepo with multiple services, each service counts as 1 deploy against your monthly limit.

For project classification, “worst wins” — if any service uses a full-stack framework, the whole project counts as 1 app:

See Full-Stack & Monorepos for deploy details, routing, and environment variables.

Scheduled Jobs

Scheduled jobs run on a cron schedule via GCP Cloud Scheduler. Each active job uses one slot from your plan.

PlanIncluded SlotsMax Timeout
Free0 (not available)
Starter15 minutes
Builder310 minutes
Pro1030 minutes

Extra slots cost 20 credits/month ($2/mo). Execution compute is consumption-based: 1 credit = 25 compute-minutes.

Credits & Overages

Credits let you go beyond your plan limits without upgrading. $1 = 10 credits, $5 minimum purchase, 12-month expiry.

Overage TypeCostPrice
Extra deploy1 credit$0.10
Extra app20 credits/mo$2/mo
Extra database15 credits/mo$1.50/mo

Organization Limits

All limits — apps, websites, deploys, databases, custom domains, and credits — are per organization, not per user or per project.

Separate organizations
If you need isolated limits, create separate organizations. Each org has its own plan, credit balance, and resource counts.

Next Steps