OPEN SOURCE · BUILDING IN PUBLIC

The infrastructure
where your AI flows
through.

Cauce is the European open source platform to build, deploy and scale robust AI agents. No vendor lock-in. No vaporware. Built to last.

Join the waitlist → See the project
Spring Boot Solid backend
Multi-tenant From the first commit
Open source No lock-in
WHY CAUCE EXISTS

There is too much
vaporware
in AI.

💸

Demos that never reach production

80% of AI agent projects you see on LinkedIn are prototypes nobody uses in production. Code without tests, without multi-tenancy, without observability.

🔒

Vendor lock-in disguised as ease

SaaS agent platforms charge you per message, tie you to their LLM, and pivot when it suits them. Your business cannot depend on that.

🧩

Integrations that do not scale

WhatsApp on one side, Telegram on another, your own API in a third repo. Each channel with its own duplicated business logic. A maintenance nightmare.

🕳️

No European reference infrastructure

Everything serious comes from the US, with prices in dollars, servers in us-east-1, and no thought for GDPR. Europe needs its own infrastructure.

“

Cauce exists because the industry has been optimising for the demo, not for production, for far too long.

It is time to build something that actually holds up.

— CAUCE OS · CAUCE.DEV
WHAT IS CAUCE

Real infrastructure.
No demos.

A modular platform that connects your channels, manages your agents memory, and exposes everything through an API. Built on Spring Boot, designed for consulting firms delivering real projects to real clients.

🌊

Multichannel from day one

WhatsApp, Telegram, voice and web chat in a single runtime. No duplicated business logic. No maintaining four separate integrations. The cauce receives every flow.

cauce-channels
🧠

Persistent memory and context

Agents remember. Memory per conversation, per user, per tenant. Support for multiple swappable LLMs without touching the agent code.

cauce-memory
🏗️

Multi-tenant and observable

Designed for a single instance to serve many clients. Metrics, traces and logs built in. Each tenant isolated from the architecture, not as an afterthought.

cauce-core
TECHNICAL STACK

Decisions made.
No compromise.

cauce-os · architecture
CHANNELS
WhatsApp
Telegram
Voice
Web / API
RUNTIME
cauce-core · agent engine + orchestration
PLATFORM
Memory
Evals
Observability
Multi-tenant
LLM
Claude
OpenAI
Gemini
+ more
API
cauce-api · REST + webhooks + admin panel
STACK Spring Boot 3.x Java 21 Gradle PostgreSQL Redis Docker
BUILDING IN PUBLIC

Built
in the open.

01

A single developer, from Spain. No funding rounds, no 20-person team, no office in Madrid. Just consistent code and honest work.

02

The whole process, in public. Every technical decision, every mistake, every refactor. If something does not work, I say so. If something works well, also.

03

The code is the documentation. No empty marketing. If you want to know whether Cauce is serious, open the repo, read the code, draw your own conclusions.

04

Europe needs its own infrastructure. GDPR, EU-based servers, Spanish as a first-class language. We are not an American fork with a European flag.

Follow the progress →

What I've built

chain · 42 units · last 2026-09-11
Breaking change unit 42 18e2401 2026-09-11

A verdict with four answers instead of two

Verification now answers VALID, BROKEN, TRUNCATED or UNVERIFIABLE, carries a signature report, and writes itself into the chain it verified. Truncation is only claimed against an anchor the caller supplies — a chain cannot detect its own missing tail.

The playground screen doesn't consume the new fields yet. A verification lands in the chain one drain tick later, not in the response that produced it.

cauce-governancecauce-apiplayground
Shipped unit 41 856b355 2026-09-11

Every audit entry now carries a signature

Ed25519 over the v2 entry hash. The private key lives in process configuration and never touches the database, so a database alone is not enough to forge an entry. The key-id to public-key registry is a file read from outside the database.

The JDK can't derive the public key from the private one, so both are configured and the pair self-checks at startup. The signature coverage report stayed internal until unit 42.

cauce-governancecauce-memorycauce-api
Shipped unit 40 94de4c0 2026-09-11

Pinning down exactly what gets hashed

The id enters the preimage, timestamps serialise at fixed microsecond precision and strings normalise to NFC, so the same entry hashes the same everywhere. Older entries aren’t recomputed; the verifier branches on the scheme each row declares.

An unknown scheme was reported as a malformed entry, which is misleading. Fixed in unit 42. The preimage spec lives in Javadoc, not in docs.

cauce-governance
Read all 42 units

Every unit links to the commit that closed it.

Be the first to
try Cauce.

We are building in the open. When we ship the first public version, the list will get access first.

No spam. Only when there is something worth it.