⚠
⚠
This service is not storing models durably. It is running without a model
directory, so every model you fit is held in memory only and will be lost on the next
restart or redeploy. Mount a volume and set KIRELTA_MODEL_DIR
before relying on it in production.
API keys
Team
Organization
Name
Logo URL
A real https:// link to an image you already host. No upload — one less thing that can go down.
Transfer ownership
Single sign-on (SSO)
Loading…
Analytics — last 30 days
Loading…
Verdict trends — last 30 days
Account
Email
—
Export your data
Downloads everything Kirelta holds about this account as a JSON file.
Export event history (CSV)
Your trust-event feed as a spreadsheet-ready CSV — a Pro+ feature.
Security
Password
Changing your password is done through the reset flow — Kirelta sends a
one-time link to your email address.
Two-factor authentication off
A code from your authenticator app, required in addition to
your password. Protects the account even if the password leaks.
1. Add this key to your
authenticator app (1Password, Authy, Google Authenticator, Microsoft Authenticator):
Choose “enter a setup key” in your app.
Account name: your email. Type: time-based.
2. Enter the 6-digit code it shows:
Save your recovery codes
Shown once. Each works a single time. Without
them, losing your authenticator means losing access to this account.
Turning this off requires your password and a
current code — a stolen session alone must not be able to lower your defences.
Sign out everywhere
Ends every active session for this account, on every device — including
this one. Use this if you suspect a session was compromised.
Billing
Plan
—
Alerts
Kirelta POSTs a trust event to this URL when a model's verdict changes — not on every reading. A model assessed a thousand times while broken sends one event, not a thousand. Point it at Slack, PagerDuty, or your own handler.
⚠
Kirelta only sees what you send it. Events fire when an assessment changes
a verdict. There is no scheduler — if your service stops calling /assess,
Kirelta goes quiet, and no event will tell you that you have gone blind. That check
belongs in your own uptime monitoring.
Kirelta notifies. It never acts on your systems — there is no remediation hook, and there will not be one added quietly.
What Kirelta will actually send — the published contract
Activity
Every key, team, and sign-in change on this account — the same append-only log referenced on the Trust & Security page.
Delete account
This erases the account, its tenant, every API key and all trained models. It cannot be undone. Export your data first if you want to keep it.