Welcome to RebelCore
Private AI for regulated work. RebelCore keeps your data in your region, governs every prompt, and audits every answer — so your team can use AI without explaining themselves to legal.
These docs cover the surfaces above that promise: how data flows in, how it’s curated, how the agent answers questions over it without leaking, and how administrators evidence the controls to auditors and regulators. The full nav is on the left; the cards below are the fast lane.
What the platform does for you
How it all fits together
It starts with your data and ends with an answer your team can defend. Three concerns sit between the two:
1. Your data, in your region
Every customer gets their own tenant — its own database, its own storage, its own audit chain — pinned to the region you pick. Data never moves out of that boundary, and the platform’s residency controls are designed to satisfy GDPR and DORA out of the box.
2. Governed end-to-end
The moment data enters the system it’s under governance:
- PII redacted before any model ever sees it — names, emails, IDs, account numbers; a leak scanner re-checks every answer before it lands back in the chat.
- Risk classification on every prompt — sensitive sessions pause for review by a DPO or Security Officer who can allow, message, or stop the user.
- Immutable audit chain — every prompt, every redaction, every reasoning step, every source cited, written once and queryable forever.
3. Scoped to the right audience
Data is only useful when the right people can ask the right questions about it. RebelCore decides that explicitly:
- Per-user roles and permissions — boolean flags, no shared back-doors, no implicit admin tiers.
- Three exposure tiers per dataset — Full, Limited, Advisory-only — set at module-build time and enforced live on every prompt the agent runs.
- Audience curation — analysts only see the datasets they’ve been granted access to; administrators only see the surfaces they need to administer.
And the agent answers within that envelope
The RebelCore Agent operates only on the data each user is permitted to see, at the exposure tier each dataset carries, with PII masked, and the whole exchange dropped into the audit trail. There’s no path around the governance layer because the agent doesn’t have one.
How the data is shaped along the way
Under all of this sits the Medallion architecture — your data flows through four curation stages, each cleaner than the last:
Bronze ──► Silver ──► Gold ──► Inference(raw) (cleansed) (curated) (agent)The agent only ever sees the Gold tier; bronze and silver stay accessible only to the small group of operators who handle raw files. The medallion is the how — data, governance and audience curation are the what.
→ Read more: Governance & access