# Claspine

> Claspine is a backend platform for building products: AI gateway, file storage, payments, audit, sign-in, permissions, notifications and more. It runs in three forms that do NOT offer the same capabilities. Check the table before planning an integration.

## Ask Claspine directly

- MCP server (Streamable HTTP, no account): https://api.claspine.com/mcp. Tools: what_runs_where, search_docs, get_guide, get_recipe, api_reference, java_api, explain_error, upgrade_notes, check_upgrade, check_code, check_config. Setup: https://claspine.com/docs/ai-agents/
- Everything in one file: https://claspine.com/llms-full.txt
- Exact calls per task: https://claspine.com/docs/recipes/ · Every error code and its fix: https://claspine.com/docs/errors/

## Three forms

- Claspine Atlas: run by Claspine at https://api.claspine.com. Your backend calls HTTP with a project API key (sp_live_... or sp_test_...) in the X-Spine-Api-Key header. Any language.
- Self-hosted engine: Docker image api.claspine.com/claspine/engine:<version> next to your app; your backend calls HTTP with a service key (ssk_...). Any language; Node.js SDK @grahmur-org/claspine-client.
- Self-hosted Spring Boot: Java modules inside a Spring Boot 3.5 application (Java 17+), from Claspine Packages (Maven/Gradle).

## Capabilities (Claspine Atlas | self-hosted engine | self-hosted Spring Boot)

- AI gateway: model routing and failover on your own provider keys: yes | yes | yes
- File storage: signed upload and download links to your own bucket: yes | yes | yes
- Payments: Stripe and Razorpay checkout, subscriptions, refunds, webhooks: yes | yes | yes
- Audit trail of Claspine’s actions, tamper-evident export: yes (console) | read-only | yes
- Write your own audit events: no | no | yes
- Scoped, expiring API keys with AI token budgets: yes | service keys with scopes | in-process
- Secret Vault for provider credentials: yes (console) | settings | settings
- Sign-in for your users (email/password, Google, Apple, phone, one-time codes) and sessions: no | yes | yes
- Permissions of signed-in users: no | read-only | yes
- Organizations, memberships, multi-tenancy, white-label brands: no | no | yes
- Feature flags and entitlements: no | no | yes
- Send email and WhatsApp from templates, through your own provider account: yes (email, WhatsApp) | yes (email, SMS, WhatsApp) | yes
- Push notifications: no | no | yes
- Custom domains and TLS certificates: no | no | yes
- Provisioning, mobile releases, store publishing: no | no | yes
- Domain packs (for example healthcare): no | no | yes
- Choose the database for Claspine’s own data: no (Claspine’s PostgreSQL) | yes | yes
- Your AI agent sets projects up for you, with your consent (MCP): yes | no | no

## Rules

- Claspine Atlas does not sign in your users, manage permissions, send push notifications or serve custom domains; it sends email and WhatsApp through the project’s own provider accounts. On Claspine Atlas keep your own login and call Claspine from your backend, passing your own stable user id.
- Browsers and mobile apps never hold a Claspine key on any form; they call your backend.
- Self-hosted Spring Boot product code uses only the platform `api` and `foundation` packages, never `internal` or `persistence`; ProductBoundaryTest enforces this.
- Every mutating platform call takes an idempotency key.

## Docs

- [What runs where](https://claspine.com/docs/what-runs-where/): the full table
- [Use Claspine with AI coding agents](https://claspine.com/docs/ai-agents/): Connect Claude Code, Cursor, Codex or Copilot to Claspine’s MCP server and give them Claspine’s rules, so they use the exact calls, fix errors and check their own work.
- [OpenAI API key](https://claspine.com/docs/openai/): Let Claspine call OpenAI models (like GPT) using your own OpenAI account.
- [Anthropic (Claude) API key](https://claspine.com/docs/anthropic/): Let Claspine call Claude models using your own Anthropic account.
- [Google Gemini API key](https://claspine.com/docs/gemini/): Let Claspine call Google’s Gemini models with a key from Google AI Studio.
- [Groq API key](https://claspine.com/docs/groq/): Let Claspine call very fast open models hosted by Groq.
- [Cerebras API key](https://claspine.com/docs/cerebras/): Let Claspine call models hosted on Cerebras’ fast inference service.
- [OpenRouter API key](https://claspine.com/docs/openrouter/): One key that reaches models from many providers, with a credit limit per key.
- [Azure OpenAI endpoint and key](https://claspine.com/docs/azure-ai/): Use OpenAI models that run inside your own Microsoft Azure subscription.
- [AWS Bedrock access key](https://claspine.com/docs/bedrock/): Use models on Amazon Bedrock through a dedicated AWS user that can do nothing else.
- [Google Vertex AI service account](https://claspine.com/docs/vertex/): Use Gemini through Vertex AI in your own Google Cloud project.
- [Amazon S3 bucket](https://claspine.com/docs/storage-aws-s3/): Store your app’s files in your own Amazon S3 bucket.
- [Cloudflare R2 bucket](https://claspine.com/docs/storage-cloudflare-r2/): Store your app’s files in Cloudflare R2, with no download fees.
- [Backblaze B2 bucket](https://claspine.com/docs/storage-backblaze-b2/): Store your app’s files in Backblaze B2.
- [Google Cloud Storage bucket](https://claspine.com/docs/storage-gcs/): Store your app’s files in Google Cloud Storage.
- [DigitalOcean Spaces bucket](https://claspine.com/docs/storage-digitalocean-spaces/): Store your app’s files in DigitalOcean Spaces.
- [Wasabi bucket](https://claspine.com/docs/storage-wasabi/): Store your app’s files in Wasabi.
- [Connect your Stripe account](https://claspine.com/docs/stripe/): Charge your own customers (one-off or subscriptions) through your Stripe account.
- [Receiving payment events in your app](https://claspine.com/docs/payment-events/): Let Claspine tell your app when a customer pays, renews, fails a payment or cancels.
- [Upgrading self-hosted Claspine](https://claspine.com/docs/upgrading/): What to do when you move your project to a newer Claspine version, release by release.
- [Install self-hosted Claspine from Claspine Packages](https://claspine.com/docs/self-hosted-packages/): Buy a license, create a download token and add Claspine’s Java and npm packages to your build.
- [Run the Claspine engine (Node.js, Python, Go and other stacks)](https://claspine.com/docs/running-the-engine/): Self-hosted Claspine for any language: a Docker image next to your app, called over HTTP or with the Node SDK.
- [Add self-hosted Claspine to an existing app](https://claspine.com/docs/add-to-existing-app/): Your app keeps its code, database and users; Claspine adds sign-in, notifications, files, AI, payments and audit next to them.
- [Sign-in with Claspine in a Spring Boot app](https://claspine.com/docs/sign-in-spring-boot/): Email and password, Google, phone codes: Claspine checks the sign-in, keeps the sessions and hands your controllers the signed-in person.
- [Sign-in with Claspine on the engine (Node.js, Python, Go)](https://claspine.com/docs/sign-in-engine/): Your backend hands the sign-in to the Claspine engine, gets a session back and checks it on every request.
- [Already have a login? Keep it](https://claspine.com/docs/keep-your-own-login/): Use Claspine’s AI, files, payments, notifications and audit without moving your users or changing how they sign in.
- [Send email and WhatsApp](https://claspine.com/docs/messaging/): Send templates to an address your backend knows, through your own AWS or mail account.
- [Email with Amazon SES](https://claspine.com/docs/messaging-email-ses/): Send email from your own domain through your AWS account.
- [Email with an SMTP service](https://claspine.com/docs/messaging-email-smtp/): Send email through the mail service you already use.
- [WhatsApp through AWS](https://claspine.com/docs/messaging-whatsapp/): Send WhatsApp messages from your own business number with AWS End User Messaging.
- [Notifications in self-hosted Claspine (email, SMS, WhatsApp, push)](https://claspine.com/docs/notifications-self-hosted/): Connect your own email, SMS, WhatsApp or push provider, write templates, and send from your code: Spring Boot or the engine.
- [Upgrading](https://claspine.com/docs/upgrading/): read every note between your version and the target before upgrading