Spending controls
Keep usage-based costs predictable with usage limits and alerts.
Usage-based billing is flexible, but flexibility shouldn't mean surprises. Silos gives you usage limits and alerts so you can stay ahead of your spend — which matters especially for automated and agent-driven workloads that can create databases on their own.
Pricing and the exact set of controls are evolving and subject to change. For current capabilities, contact us.
Limits and alerts
Usage limits
Set a ceiling on usage so consumption can be capped before it runs away.
Usage alerts
Get notified as usage approaches a threshold you care about, so there's no end-of-month surprise.
Usage visibility
Monitor consumption by dimension in the Console and via the usage API to see what drives cost.
Configure these from the Console's billing and usage settings.
Watching usage programmatically
For automated environments, read usage from the REST API and act on it in your own tooling — for example, to pause or tear down databases when a workload finishes:
curl "https://api.silos.sh/v1/projects/{project_id}/usage" \
-H "Authorization: Bearer $SILOS_API_KEY"Patterns that keep spend down
- Let idle databases scale to zero. Don't keep databases warm unless a hot path needs it — idle databases don't bill compute. See Scale to zero.
- Tear down ephemeral databases. For agent and CI workloads, delete databases when the work is done rather than leaving them allocated. See Ephemeral databases.
- Right-size your plan. Match your plan to the service-level target and capacity you actually need.