Console ➔ Get Spine · $499
GIVE YOUR AGENTS A SPINE

Your AI agent vs. the build.

Spine is the enterprise backend OS your AI agents can't break. 20 platform modules out of the box — plus guardrails that fail the build the moment an agent takes a shortcut.

Start building with Spine from $499 · one-time See how it works ↓
Built for teams shipping withCursorClaude CodeDevinCodexAntigravity

AGENT VS. BUILD

starring Spine
DEMO · THE AGENT IS PLAYING ITSELF

← → / A D / swipe to switch lanes · grab capabilities · try the shortcuts
01 · HOW TO PLAY

The game is rigged. In your favor.

That arcade machine is a cartoon of the real thing. Spine ships ArchUnit boundary tests inside the platform. When an agent crosses a boundary, ProductBoundaryTest fails the build — the agent reads the failure, self-corrects and follows the enterprise pattern.

SELECT A SHORTCUT
  1. 1Agent grabs a shortcut
  2. 2The build blocks it — before it can merge
  3. 3Agent reads the error and levels up
AGENT.EXE · PLAYER 1 READY

Example agent sessions

Import storage internals

PLAYER 1 · AGENT.EXE · LEVEL 1
> quest: let users upload a profile photo
> shortcut spotted. grabbing it…
+ import com.grahmur.platform.modules.files.internal.s3.S3StorageProvider;
$ ./mvnw test
✕ ProductBoundaryTest FAILED · product_consumes_only_platform_contracts
✕ BUILD FAILURE
> reading the error… new strategy
- import com.grahmur.platform.modules.files.internal.s3.S3StorageProvider;
+ import com.grahmur.platform.modules.files.api.FileStorage;
$ ./mvnw test
✓ BUILD SUCCESS · guardrails green · +1000 XP

Query the platform database

PLAYER 1 · AGENT.EXE · LEVEL 2
> quest: load the signed-in user’s account
> shortcut spotted: read the account collection
+ import com.grahmur.platform.modules.identity.persistence.IdentityAccountMongoRepository;
$ ./mvnw test
✕ ProductBoundaryTest FAILED · product_consumes_only_platform_contracts
✕ BUILD FAILURE
> reading the error… new strategy
- import com.grahmur.platform.modules.identity.persistence.IdentityAccountMongoRepository;
+ import com.grahmur.platform.modules.authentication.api.AuthenticatedPrincipal;
$ ./mvnw test
✓ BUILD SUCCESS · guardrails green · +1000 XP

Reach into LLM internals

PLAYER 1 · AGENT.EXE · LEVEL 3
> quest: summarize support tickets with an LLM
> shortcut spotted: grab the orchestrator directly
+ import com.grahmur.platform.modules.llm.internal.LlmOrchestratorService;
$ ./mvnw test
✕ ProductBoundaryTest FAILED · product_consumes_only_platform_contracts
✕ BUILD FAILURE
> reading the error… new strategy
- import com.grahmur.platform.modules.llm.internal.LlmOrchestratorService;
+ import com.grahmur.platform.modules.llm.api.LlmService;
$ ./mvnw test
✓ BUILD SUCCESS · failover unlocked · +1000 XP
02 · ENEMY ROSTER

Meet the AI slop bosses.

Spawned by coding agents optimizing for the demo instead of enterprise longevity. Each one is an instant fail in a vendor security review.

FINAL BOSS · 01CRITICAL

The Key Leaker

const KEY = "sk_live_…"

Hides live secrets in the client bundle.

DAMAGE TO DEALTAKING DAMAGE…
BOSS 02CRITICAL

String Glue

"… org='" + req.query.org

Builds SQL by concatenating user input.

DAMAGE TO DEALTAKING DAMAGE…
BOSS 03HIGH

Tenant Hopper

await Invoice.find()

Serves every customer everyone’s data.

DAMAGE TO DEALTAKING DAMAGE…
BOSS 04HIGH

The Loud Logger

console.log(authorization)

Writes bearer tokens to production logs.

DAMAGE TO DEALTAKING DAMAGE…
BOSS 05MODERATE

Byte Hoarder

s3.putObject(req.body.file)

Squeezes every upload through app memory.

DAMAGE TO DEALTAKING DAMAGE…
03 · POWER-UPS

20 modules. All unlocked on day one.

No grinding. Every module is pre-built and covered by 700+ automated tests. Six of the load-bearing ones:

Identity & access

Opaque, deployment-bound sessions; provider-verified credentials; exact runtime-context authorization with direct permission grants.

  • Sessions
  • Firebase verifier
  • Runtime authz
  • Memberships

Direct storage

Presigned uploads and downloads — clients go straight to the cloud, zero bytes through your backend.

  • S3
  • GCS
  • Azure Blob

BYOD persistence

Platform state runs on PostgreSQL, MongoDB-compatible stores or Firestore — you pick with one setting. Your own domain data can live in any database.

  • PostgreSQL
  • MongoDB Atlas
  • DocumentDB
  • Cosmos (Mongo API)
  • Firestore

AI orchestration

Multi-provider model routing with free-tier failover chains and paid tiers on your own cloud credits.

  • Bedrock
  • Vertex AI
  • Azure AI
  • OpenAI
  • Anthropic
  • Gemini
  • Groq
  • Cerebras
  • OpenRouter

Notifications

Idempotent delivery with provider adapters and product-owned templates, including approved WhatsApp templates.

  • SES
  • SNS
  • Twilio
  • FCM
  • WhatsApp

Audit & secrets

Fail-closed audit: if the event can’t be written, the operation doesn’t proceed. Secrets and tokens are filtered from audit data.

  • Fail-closed
  • Secret filtering
  • Opaque credential refs

Spine provides controls that support HIPAA, SOC 2 and GDPR programs (fail-closed audit, secret scrubbing, deployment-bound sessions). It is compliance-ready, not certified: using Spine does not by itself make a product compliant, and your organization remains responsible for its own compliance.

04 · CO-OP MODE

Engineered for polyglot teams.

Whether you write Spring Boot in-process or build your product API in Next.js or Express with the typed Node.js SDK, Spine OS is the unbending infrastructure core underneath.

Languages & frameworks

Integration model and status by language
Language / frameworkIntegration modelStatus
TypeScript / Node.jsNext.js · Express · Fastify · Bun Official typed SDK@grahmur-org/spine-client on npm (Apache-2.0, zero dependencies). Covers authentication, permissions, audit, notifications, host/brand resolution and bootstrap. Express and Next.js middleware included. SHIPPED
Java / JVMSpring Boot 3 In-process modules, starters & BOMMaven artifacts com.grahmur:grahmur-platform-* with all 20 modules. Depend on the umbrella, a lean starter, or individual modules. SHIPPED
Python · Go · anything with HTTPFastAPI · Django · Gin · … REST + webhook APIsThe platform exposes versioned HTTP endpoints (/api/v1/*) and delivery webhooks. No official SDK yet; call it like any JSON API. REST ONLY
$ npm install @grahmur-org/spine-client

The SDK connects to a Spine engine service that you run in your own cloud over HTTP. A prebuilt engine container image is not published yet, and the SDK does not cover files, LLM routing or payments today.

Bring your own database

Never migrate your database to fit a backend. Point Spine OS at the PostgreSQL, MongoDB or Firestore you already run. It manages its own platform_* tables and leaves your business tables untouched.

Supported database engines and services
EngineServicesWhy builders care
PostgreSQLRelational / SQL
  • Supabase
  • Neon
  • AWS RDS
  • Google Cloud SQL
  • Azure Database for PostgreSQL
  • Self-hosted
 29 platform_* tables via plain JDBC: no JPA or Hibernate. Keep using Prisma, Drizzle, Kysely or JPA for your own tables in the same database.
MongoDBDocument / NoSQL
  • MongoDB Atlas
  • AWS DocumentDB
  • Azure Cosmos DB (Mongo API)
  • Self-hosted
 Flexible documents, optimistic-locking revisions, and the managed clusters you already run.
Cloud FirestoreServerless NoSQL
  • Google Cloud Firestore
 Serverless scale with a dependency-free JDK client; no MongoDB cluster required.

Select the engine with platform.persistence.type (postgres, mongo or firestore). Spine creates its platform_* tables on first boot, which you can turn off. Named services are common targets for standard PostgreSQL and MongoDB, not per-provider certifications.

Cloud & infrastructure compatibility

Object storage

Direct-to-cloud presigned uploads and downloads

  • AWS S3
  • Google Cloud Storage
  • Azure Blob Storage

AI gateways

Multi-provider routing with failover chains

  • Amazon Bedrock
  • Google Vertex AI
  • Azure AI Foundry
  • OpenAI
  • Anthropic

Transactional comms

Queued delivery with retries and provider adapters

  • WhatsApp Business (via AWS End User Messaging)
  • Amazon SES
  • Twilio SMS
  • Amazon SNS
  • Firebase FCM
05 · WORLD MAP

One open door. Two sealed worlds.

A strict in-process modular architecture. Your product can only travel through api. There are no warp pipes into internal or persistence.

  • WORLD 0 · START

    Your product

    Domain logic. Any database — PostgreSQL via JPA included.

    YOU ARE HERE ▶
  • WORLD 1 · api

    Public ports

    The only door into the platform.

    ✓ OPEN
  • WORLD 2 · internal

    Implementations

    Sealed. No warp pipes.

    ✕ LOCKED
  • WORLD 3 · persistence

    Platform stores

    PostgreSQL · MongoDB · Firestore. Sealed.

    ✕ LOCKED
TRAVEL FROM YOUR PRODUCT TO →
PICK A WORLD. YOUR AGENT WILL TRY TO WALK THERE.
FOR SECURITY REVIEWERS & TEAM LEADS

Evaluating Spine for your team? Skip the arcade.

A plain-language architecture overview, the boundary model, the security controls and where responsibility sits, on one page you can forward or save as a PDF.

Architecture & security summary Talk to us
06 · SELECT MODE

CONTINUE?

Rebuilding the backend yourself costs 4–8 months and $100k+ in payroll. Or buy it once. No subscriptions. Source-available, debug symbols intact.

1 PLAYERFounder / Startup

US dollars $499

ONE COIN · ONE TIME
  • ▸ 1 production application
  • ▸ All 20 platform modules
  • ▸ Starter source + debuggable platform artifacts
  • ▸ Boundary guardrails + 700+ tests
  • ▸ 1 year of releases & security updates
GET THE FOUNDER LICENSE
MULTIPLAYERAgency / Studio

US dollars $1,999

UNLIMITED CONTINUES
  • ▸ Unlimited client projects
  • ▸ White-labeling permitted
  • ▸ Starter source + debuggable platform artifacts
  • ▸ Boundary guardrails + 700+ tests
  • ▸ 1 year of releases & security updates
GET THE AGENCY LICENSE

One-time price per license. Terms are set by the Commercial License Agreement from GRAHMUR OÜ. Buying for a security review or a team? Read the architecture & security summary.

07 · HINTS & TIPS

Questions before you press start.

Straight answers, including what Spine does not do. More detail for security reviewers is on the architecture & security page.

What is Spine OS?

Spine OS is a commercial, source-available Java 17 / Spring Boot 3.5 backend platform, with an open-source TypeScript client for Node.js teams. It ships 20 ready-made modules (identity, authentication, authorization, files, LLM orchestration, notifications, audit, payments and more) plus an ArchUnit test, ProductBoundaryTest, that fails the build when product code reaches into platform internals.

How do the guardrails work, and what do they not cover?

ProductBoundaryTest runs with ./mvnw test. It fails if product code depends on platform internal or persistence packages or on Spring Data. That stops an AI agent from bypassing the public api contracts. It does not review your business logic or scan for every insecure pattern; secret handling, audit and session security come from the platform modules you call, not from this one test.

Is Spine OS HIPAA, SOC 2 or GDPR compliant?

Spine provides controls that support HIPAA, SOC 2 and GDPR programs (fail-closed audit, secret scrubbing, deployment-bound sessions). It is compliance-ready, not certified: using Spine does not by itself make a product compliant, and your organization remains responsible for its own compliance. Have your own auditor or counsel validate your deployment.

Do I get the source code?

Yes. You get the Spine starter repository (application wiring, product adapters, AI rule files such as AGENTS.md) as source. The platform core is delivered as versioned Maven artifacts with line numbers and debugging symbols intact and no obfuscation, so you and your AI agent can step through it. Redistribution is limited by the commercial license.

Which databases does it support?

Platform state (sessions, audit events, notification deliveries and so on) runs on PostgreSQL, MongoDB-compatible stores (Atlas, AWS DocumentDB, Azure Cosmos DB Mongo API) or Google Firestore, selected with platform.persistence.type. Your own product data is independent: use any database and any ORM, and its tables are never touched because platform tables are prefixed platform_.

Can I use Spine from TypeScript or Node.js?

Yes, for the capabilities the client covers. The open-source @grahmur-org/spine-client SDK (Apache-2.0) gives Next.js, Express and other Node apps typed access to authentication, permissions, audit, notifications and host/brand resolution. It talks over HTTP to a Spine engine service that you run; a prebuilt container image is not published yet. Files, LLM routing and payments are not in the SDK today.

Can I add Spine to an existing Spring Boot app?

Yes. Add the dependency to your existing pom.xml; the modules auto-configure through standard Spring Boot auto-configuration, so no scanBasePackages changes are needed, and platform tables are prefixed platform_ so they do not collide with yours. You can also depend on individual modules or on the leaner starters.

What do the licenses include?

Founder / Startup ($499, one-time): one production application and one year of platform releases, provider adapters, security updates and documentation. Agency / Studio ($1,999, one-time): unlimited client projects, white-labeling permitted, same one year of updates. The full terms are in the Commercial License Agreement from GRAHMUR OÜ.