slot-scale
Slot Scale
Scale deployments from development to production with paid tiers, replicas, and multi-region.
Instance Tiers
| Tier | Specs | Storage | Cost |
|---|---|---|---|
| Basic | Limited CPU & memory | 1GB | $10/month |
| Pro | 2 vCPU, 4GB RAM | auto | $50/month |
| Epic | 4 vCPU, 8GB RAM | auto | $100/month |
| Legendary | 8 vCPU, 16GB RAM | auto | $200/month |
First 3 Basic tier deployments are free. Storage on premium tiers: $0.20/GB/month (auto-scaling).
Basic tier behavior
- Scaled down automatically after a few hours of inactivity
- Revived on first request
- Deleted if unused for 30+ days
Premium tiers (Pro+)
- Never scaled down or deleted while the team has credits
- Auto storage scaling (never runs out of disk space)
Replicas
Torii supports multiple replicas on premium tiers:
slot d create --tier epic my-project torii --replicas 3
Billed per replica (3 replicas = 3× tier cost). Katana does not support replicas.
Regions
| Region |
|---|
us-east |
europe-west |
Deploy in multiple regions with --regions:
# Torii: multi-region with replicas
slot d create --tier pro my-project torii --regions us-east,europe-west
# Katana: single region only
slot d create --tier pro my-project katana --regions europe-west
Billing: tier cost × regions × replicas.
Creating Paid Tier Deployments
Ensure the team has credits (see slot-teams skill), then:
slot d create --tier epic --team my-team my-instance torii
Upgrading an Existing Deployment
Tiers can only be upgraded, not downgraded:
slot d update --tier epic my-instance torii
The team that owns the deployment must have sufficient credits.
More from cartridge-gg/docs
controller-setup
Integrate Cartridge Controller wallet into Starknet applications. Use when setting up Controller for the first time, installing packages, configuring chains/RPC endpoints, or troubleshooting basic integration issues. Covers installation, Controller instantiation, ControllerConnector vs SessionConnector choice, chain configuration, and package compatibility.
69controller-sessions
Configure session keys and policies for Cartridge Controller to enable gasless, pre-approved transactions. Use when defining contract interaction policies, setting spending limits, configuring signed message policies, or implementing error handling for session-based transactions. Covers SessionPolicies type, policy definitions, verified sessions, and error display modes.
68controller-react
Integrate Cartridge Controller into React applications using starknet-react. Use when building React/Next.js web apps with Controller, setting up StarknetConfig provider, using hooks like useConnect/useAccount, or implementing wallet connection components. Covers ControllerConnector setup, provider configuration, and transaction execution patterns.
67controller-signers
Configure authentication methods for Cartridge Controller including passkeys, social login, and external wallets. Use when implementing user authentication, adding multiple signers for account recovery, customizing signup options, or integrating external wallets like MetaMask or Phantom. Covers WebAuthn passkeys, Google/Discord/Twitter OAuth, wallet connections, and dynamic authentication flows.
65controller-backend
Integrate Cartridge Controller into backend services using Node.js, Rust, or headless mode. Use when building server-side applications, game backends, automated bots, or any non-browser environment that needs to execute Starknet transactions. Covers SessionProvider for Node.js, Rust SDK setup, and headless Controller with custom signing keys.
61slot-vrng
Integrate Cartridge's verifiable random number generator (vRNG) into onchain games.
59