Skip to content
LAUNCH FILM — LIVEGREENLIGHT · PATENT-PENDINGRUNTIME AUTHORIZATION FOR AI AGENTSMCP CONNECTORS — IN DESIGNISO/IEC 27001 — ROADMAPSOC 2 TYPE II — ROADMAPISO/IEC 42001 — ROADMAPMAS FEAT — DESIGN-ALIGNEDDETERMINISTIC · EXPLAINABLE · TAMPER-EVIDENTAI ACTS · CRELIS DECIDESLAUNCH FILM — LIVEGREENLIGHT · PATENT-PENDINGRUNTIME AUTHORIZATION FOR AI AGENTSMCP CONNECTORS — IN DESIGNISO/IEC 27001 — ROADMAPSOC 2 TYPE II — ROADMAPISO/IEC 42001 — ROADMAPMAS FEAT — DESIGN-ALIGNEDDETERMINISTIC · EXPLAINABLE · TAMPER-EVIDENTAI ACTS · CRELIS DECIDES
Crelis.ai

Security & Trust

Security & trust, by design

Crelis is built to be handed to a security review. It currently runs in our hosted pilot environment, decides on decision metadata rather than raw customer data, and records every decision in a tamper-evident audit trail.

Decision metadata, not raw data

Crelis decides on decision metadata — action types and results, e.g. “identity: not verified”, “amount > limit”. A decision needs the category and the outcome, not the sensitive value, so your integration keeps raw customer data out of the request.

Hosted service

Crelis currently runs in our hosted pilot environment — today in shadow posture, with no customer deployments yet. Deployment options beyond our hosted service are on the roadmap.

Tenant isolation

Server-enforced isolation with a production guard. Cross-tenant access is denied — not merely hidden in the UI.

Tamper-evident audit

Every decision is written to a durable, tamper-evident record — show what was decided, and prove it has not been altered since.

Deployment

Where it runs today, and where it is going

Crelis sits beside your systems, not inside your model. Today it runs in our hosted pilot environment; deployment options beyond our hosted service are on the roadmap.

Hosted service (SaaS)

Runs in our environment with server-enforced tenant isolation. This is where the 2026 design-partner cohort runs.

Pilot

Deployment options beyond our hosted service

Dedicated and customer-controlled deployment models are on the roadmap — not available today. Crelis is delivered as a hosted service only.

Roadmap

Data handling

Decision metadata, not raw customer data

What Crelis stores

  • · Decision metadata — action types, results, policy outcomes
  • · Trust signals as types/results (e.g. “identity: not verified”)
  • · Tamper-evident audit records of each decision

What Crelis does not store

  • · Raw identity, card, or document numbers
  • · Customer names, contact details, or message contents
  • · Any field the calling system doesn’t send for a decision

The shape is structural — a Crelis decision is made on categories and outcomes, not sensitive values, so the integration keeps raw values out of the request rather than relying on a setting. In transit, all traffic uses TLS 1.2+; at rest, provider-managed encryption applies; keys are held server-side and never exposed to the browser.

Frameworks

Aligned with how your examiners think

Crelis is built around the principles in these frameworks. This denotes design alignment, not certification — Crelis does not currently hold SOC 2, ISO 27001, or ISO 42001 certification; formal certification is planned as we mature.

MAS FEAT

Fairness, ethics, accountability, transparency — deterministic, explainable, human-in-the-loop decisions with audit.

IMDA Model AI Governance / AI Verify

Explainability, human oversight, and record-keeping for AI-driven actions.

ISO/IEC 42001

An AI management-system mindset: policy lifecycle, roles, logging, continual oversight.

Reviewing Crelis for your team?

Request the full Security & Trust Pack, or send your security questionnaire — we’ll turn it around quickly.

Request the Security & Trust Pack
Apply for Pilot Access