CLASPINE ATLAS · SETUP GUIDES
Connect your accounts
Claspine Atlas uses your own provider accounts, so you keep control of costs and data. Each guide shows where to find the values the console asks for, and how to create a key that can do only what Claspine needs.
AI agents
Use Claspine with AI coding 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.
AI Models
OpenAI API key
Let Claspine call OpenAI models (like GPT) using your own OpenAI account.
Anthropic (Claude) API key
Let Claspine call Claude models using your own Anthropic account.
Google Gemini API key
Let Claspine call Google’s Gemini models with a key from Google AI Studio.
Groq API key
Let Claspine call very fast open models hosted by Groq.
Cerebras API key
Let Claspine call models hosted on Cerebras’ fast inference service.
OpenRouter API key
One key that reaches models from many providers, with a credit limit per key.
Azure OpenAI endpoint and key
Use OpenAI models that run inside your own Microsoft Azure subscription.
AWS Bedrock access key
Use models on Amazon Bedrock through a dedicated AWS user that can do nothing else.
Google Vertex AI service account
Use Gemini through Vertex AI in your own Google Cloud project.
File Storage
Amazon S3 bucket
Store your app’s files in your own Amazon S3 bucket.
Cloudflare R2 bucket
Store your app’s files in Cloudflare R2, with no download fees.
Backblaze B2 bucket
Store your app’s files in Backblaze B2.
Google Cloud Storage bucket
Store your app’s files in Google Cloud Storage.
DigitalOcean Spaces bucket
Store your app’s files in DigitalOcean Spaces.
Wasabi bucket
Store your app’s files in Wasabi.
Payments
Connect your Stripe account
Charge your own customers (one-off or subscriptions) through your Stripe account.
Receiving payment events in your app
Let Claspine tell your app when a customer pays, renews, fails a payment or cancels.
Self-hosted
Upgrading self-hosted Claspine
What to do when you move your project to a newer Claspine version, release by release.
Install self-hosted Claspine from Claspine 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)
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
Your app keeps its code, database and users; Claspine adds sign-in, notifications, files, AI, payments and audit next to them.
Sign-in
Sign-in with Claspine in a Spring Boot app
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)
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
Use Claspine’s AI, files, payments, notifications and audit without moving your users or changing how they sign in.
Messaging
Send email and WhatsApp
Send templates to an address your backend knows, through your own AWS or mail account.
Email with Amazon SES
Send email from your own domain through your AWS account.
Email with an SMTP service
Send email through the mail service you already use.
WhatsApp through AWS
Send WhatsApp messages from your own business number with AWS End User Messaging.
Notifications in self-hosted Claspine (email, SMS, WhatsApp, push)
Connect your own email, SMS, WhatsApp or push provider, write templates, and send from your code: Spring Boot or the engine.
Keys and least privilege
- Never paste root or administrator keys into any service, including Claspine. Create a dedicated key or user for Claspine.
- Give that key only what Claspine uses; each guide lists the exact permissions. If it leaks, the damage stays inside that scope.
- Set spending limits or budget alerts at the provider, since AI and storage are billed to your account.
- Claspine stores keys encrypted, shows them only masked, and never sends them to your app or SDK. Replace or remove a key in the console at any time; revoke the old one in your provider’s console.