Now in alpha

Private AI orchestration for SimpleX and Matrix communities

Local AI, human controlled agents, autonomous NPCs, consent first community memory and a hardened administration platform. One embedded core, your own infrastructure, and no silent cloud fallback.

Consent firstPasskeysLocal AIAGPL-3.0
CIND3R3LLA Consent first
Open source

Run it yourself

CIND3R3LLA is free software under the GNU Affero General Public License v3.0. Read every line, run it on your own infrastructure, and modify it. An archive asks a community for trust, and the licence is what makes that trust checkable rather than promised.

archive.cinderella.example / all groups PREVIEW · SAMPLE DATA
10 messages
mara#privacy-talk14:02 archived
New onion-routing writeup is up, covers guard selection end to end.
devnull#privacy-talk14:03 archived
Does it touch on padding overhead? That's where most guides hand-wave.
kai#selfhosting09:11 archived
Here's my docker-compose.yml for the archive bot behind Caddy.
attachment
lena#selfhosting09:14 archived
meetup_recording.mp4
video · behind auth
tomasz#foss-de21:40 archived
AGPL vs GPL for a bot serving a public archive, 14 replies deep now.
mara#privacy-talk14:20 archived
Passkey rollout checklist v2 attached: WebAuthn only, no fallback.
attachment
ingrid#foss-de21:52 archived
Onion services plus this archive = searchable history without a central host.
kai#selfhosting10:02 archived
grafana-dashboard.png: capture throughput over 24h.
image · behind auth
devnull#privacy-talk15:31 archived
Consent prompt fired before capture, logged with the group id. Clean.
tomasz#foss-de22:05 archived
Full-text search across a year of threads in under 40 ms.
No archived messages match
What it is

A control plane for intelligent identities

CIND3R3LLA is a self hosted control plane for intelligent identities inside private and public communities. It brings the embedded core, deterministic application logic, local language models, persistent community memory, human supervision, moderation workflows, knowledge publishing and character driven interaction together in one platform, running on hardware you control.

Capabilities

What the platform does

The consent first archive is one capability among several, not the product.

Local AI runtime

Inference runs against your own Ollama endpoint, with independent model routing for intent classification and for reply wording. Connections are probed before activation, a missing model refuses to activate, and when the model is unavailable the deterministic rule engine answers. There is no silent cloud fallback.

Multi profile identities

One embedded core hosts many persistent profiles without one process per bot. Actor type, automation mode, personality, permissions, avatar source and public role are separate settings: a fantasy avatar does not decide whether an identity is human operated, autonomous or purely technical.

NPCs and characters

Autonomous characters host games, explain features, welcome new members, tell context aware jokes and create roleplay moments. Scheduling, permissions, context access, message limits and cooldowns are deterministic. The model supplies the wording, never the decision.

Human operated agents

A moderator works through a persistent avatar, discusses difficult situations with the team in a private staff space, refines the behaviour, and continues in the public conversation as the same identity. Assisted mode, autopilot and immediate human takeover, with approval requirements and an audit history.

Consent first community memory

Opted in conversation becomes a searchable public archive the community owns. Publication is derived from consent on every read rather than stored as a flag, so a withdrawal takes effect everywhere at once, and the member then chooses whether their words are hidden or destroyed.

Administration platform

Every capability has a real control, a stored setting shown separately from its effective runtime state, audit coverage and documented failure behaviour. No hidden behaviour, and no controls that are not wired to anything.

Moderation and safety

Public reporting, an operator review queue, audited takedowns, evidence holds that defer destruction without ever delaying hiding, and quarantine that moves material out of the served tree entirely.

Self hosted under AGPL

Your server, your database, your models, your rules. The source is AGPL 3.0, so anyone operating a modified version owes their users the same freedoms. No cloud dependency and no vendor in the middle of your community.

Human control

The model never gets authority

This is the line the whole architecture is drawn around. AI may classify a message and phrase a reply. It never receives permission to execute, to change consent, to publish, or to send arbitrary messages. Identity, permissions, routing, publication and execution stay in deterministic application code.

A responsible human stays behind every supervised identity and can observe, interrupt, edit, approve or take over at any moment.
A human operated identity is never silently converted into an autonomous one.
Nobody can publish or unpublish on another member’s behalf, not an administrator, not the operator, not the model.
Security

Part of the architecture, not a checkbox

Passkeys as the primary administrative login, an admin console bound to loopback behind TLS, originals encrypted at rest, metadata stripped before publication, and every state changing action written to an audit trail.

Passkeys first, with a break glass path the operator controls
Media originals encrypted at rest, public copies stripped of metadata
Consent enforced in the database view, not in a flag somebody can forget
Audit coverage on every administrative action