11 posts tagged with "api"

SphereFiles: shared file volumes. You can now add a file volume to an environment and mount it into several services at once, for uploads, media or shared assets.

The type in every error the API returns now points at the docs' new home: https://computesphere.com/docs/errors/<code> instead of https://docs.computesphere.com/errors/<code>. The docs_url of each field in a validation error now links to the code's page (the #field fragment is gone).

When you turn on public access for a database, its hostname now starts with the database's name, for example orders-api-7k2m9q.us-east-1.db.computesphere.com.

SphereCache now goes up to Cache 10 GB.

You can now add a managed Valkey cache to any environment, next to your services, at a fixed monthly price.

You can now add a RabbitMQ message broker of your own to any environment, next to your services, at a fixed monthly price.

Create managed PostgreSQL databases in EU (Sweden), eu-north-1. It's open to every account, on every plan from Free to Plus.

Choose which variables your build can read, run migrations before a release takes traffic, and ship the exact image you tested in one environment to another without rebuilding it.

Every error returned by the ComputeSphere API now ships with a stable code and a direct link to its catalog entry — paste the URL into Claude, Cursor, or ChatGPT and they have full context for debugging.

New signups must verify their email address before creating their first project. Existing accounts are unaffected.

The new v2 API is live at api.computesphere.com/v2. Predictable response envelope, stable error codes, and a published OpenAPI spec that's the source of truth for every client we ship.