scaledbox documentation

scaledbox cloud runs your SaaS products, and your customers' apps, on servers it owns and operates. You declare what a product needs and the most it may spend; scaledbox places it, deploys it, gives it databases, object storage and certificates, and keeps it within its limit.

Start here

• Getting started: install the CLI, sign in, ask for a product, deploy it.
• scaledbox.toml reference: every setting of a product's file.

Guides

• Deploying: services as boxes of your built modules, releases and their migrations, rollbacks, capacity, logs, secrets, environments and previews, database dumps.
• Deploying from CI: deploy tokens, building your modules, a GitHub Actions workflow.
• Domains: your product's own names, proven by DNS records, with HTTPS.
• Tenants: the API your product uses to run its customers' apps.
• Develop locally: a tenant's app on your machine as a deploy would run it, and the SDK your own tools drive it with.
• Spending: credits, budgets, what is billed and how limits work.
• Status pages: your product's public status page at a name of its own.
• Limits: sizes, defaults and rate limits in one place.
• Acceptable use: what apps on scaledbox may not do.

The API

The CLI and the console use the public API at https://api.scaledbox.dev, and so can your product and its CI. Its OpenAPI document is at api.scaledbox.dev/openapi.yaml, with a browsable reference at api.scaledbox.dev/docs. Every request carries a token: Authorization: Bearer sbx_....