Security
Built to be trusted with your source code.
Yakini reads repositories, tickets and delivery systems, and publishes findings about people’s work. It is designed on three assumptions: data must never cross organizations, any input may be hostile, and leaders never learn something an engineer hasn’t had the chance to answer. This page describes the controls as they are built today.
At a glance
As built today- Row-level security on every tenant table
- AES-256-GCM data keys per organization
- OIDC and SAML 2.0 single sign-on, SCIM 2.0, MFA
- 13 roles over 44 permissions, plus custom roles
- An append-only, hash-chained security log
- Self-hosted models and private runners
Tenant isolation
The database keeps organizations apart.
Isolation doesn’t depend on every query being written correctly: PostgreSQL enforces it.
- Row-level security on every tenant table; requests run as a database role that can’t bypass it, so a missing filter can’t leak another organization’s rows
- A separate platform role only where it’s unavoidable, such as scheduling jobs across organizations
- Files, Git mirrors, source snapshots and code indexes stored under each organization’s own path
- Automated tests check that PostgreSQL itself rejects reads and writes across organizations
Encryption and keys
Secrets stay encrypted, and stay secret.
Each organization has its own data keys, and Yakini never shows a stored secret again.
- Data keys per organization (AES-256-GCM), wrapped by the platform’s key-encryption key
- Connector credentials, webhook secrets, model API keys and single sign-on secrets stored only encrypted; screens show fingerprints, never secrets
- Key rotation re-encrypts stored credentials under a new data key, and the master key can be rotated too
- Stored files such as proof packages, reports and exports encrypted at rest: with the organization’s own key on the default file store, or by the bucket’s server-side encryption on S3
- Proof packages and reports signed with Ed25519; outbound webhooks signed with HMAC-SHA256
Encryption at rest of the database itself is provided by the infrastructure it runs on.
Deployment
Run it where your code is allowed to go.
Hosted, hosted with a private runner, dedicated or self-hosted: the same product in each.
Your network
Repository code stays here- Code index
- Verification lab
- Auditor
- Citation checks
Stays inside
- Repository code
- Test execution and its output
- Code excerpts, by default
HTTPS, outbound only
The audit record and result
Reduced by your outbound policy
- Verdicts, confidence and reasoning
- File paths, lines and symbols
- Tests run and their outcomes
Yakini
- With a private runner, repository code and test execution stay in your network; only the audit record and result leave it, reduced by an outbound policy you set
- By default, a private runner sends no code excerpts: locations, reasoning and results only
- Self-hosted with Kubernetes and Helm, Docker Compose or systemd; Terraform installs the Helm chart
- Outbound calls refuse private network addresses unless you allow them, and production requires HTTPS
Four ways to run it
The same product and the same controls in each.
- Hosted
- Hosted with a private runner
- Dedicated
- Self-hosted
AI governance
Models work for you, under your rules.
You decide which models see what, and the auditor works inside hard limits.
Your models, task by task
The provider and model for each task are yours to choose, including self-hosted models; each provider is registered with its region and whether it may receive source code. Audits stop rather than send code to a model that isn’t allowed to receive it.
Untrusted input, treated as data
Code, tickets and logs are treated as untrusted data: scanned for prompt injection, with secrets in known formats redacted before they reach a model.
Hard budgets, and no guessing
Hard budgets for tool calls, tokens, time and cost. When a budget runs out, the verdict is Unverified, not a guess.
Read-only tools, people in charge
The auditor’s tools are allow-listed and read-only, and definitive verdicts can be held for human approval.
Yakini trains no models on your code, and each organization decides which providers may receive source code.
Identity and access
Your identity provider, your roles.
People sign in the way your organization decides, and see only what their roles allow.
Sign-in
- Single sign-on with OIDC or SAML 2.0, routed by verified email domains, with just-in-time accounts and group-to-role mapping; it can be made mandatory
- SCIM 2.0 provisioning and deprovisioning; removing someone ends their sessions at once
- Multi-factor authentication with an authenticator app, and single-use recovery codes
Roles and scopes
- 13 built-in roles over 44 permissions, plus custom roles, for the whole organization or scoped to a business unit, team or project, optionally with an expiry
- Every permission is checked on the server, on every request
Source access
- Source access is separate: restricted repositories need an explicit grant, and people without one see findings without code
Audit trail
A record that shows if anything changed.
What happened, and who did it, is kept in a form you can check.
Security-relevant changes written to an append-only log, hash-chained per organization; recomputing the chain shows whether anything was altered
Investigation records, evidence and policy versions are append-only too
Published verdicts never change: a new audit version supersedes them, and the history stays
Retention and deletion
Keep what you need, for as long as you need it.
Cached copies of your code don’t outlive their use, and evidence can be put on hold.
- Cached source code removed once unused for the period you set, from 1 to 365 days (30 by default), and can be purged at any time
- Legal hold blocks deletion of evidence
- Deleting an organization takes effect after a grace period, and waits while a legal hold is on
- A signed export of the organization’s records, without secrets, for people with the right permissions
Compliance readiness
Mapped to the frameworks you report against.
Yakini maps its technical controls to SOC 2, ISO/IEC 27001, the GDPR and the Kenya Data Protection Act, to support your own due diligence.
- Controls mappedSOC 2
- Controls mappedISO/IEC 27001
- Controls mappedGDPR
- Controls mappedKenya Data Protection Act
No certification, attestation, audit or assessment has been performed. Compliance belongs to the organization that runs a system; Yakini provides technical controls and documents what it doesn’t provide.
We work through your security review and data-processing terms. Write to security@yakini.io to start one.
Report a vulnerability
Found a security problem? Tell us.
security@yakini.ioEmail us with:
- What you found
- Where you found it
- The steps to reproduce it
We’ll reply by email.
While you look into it, please don’t access or change other people’s data, don’t disrupt the service, and give us a fair chance to fix the problem before you make it public.
Bring your security questions.
We’ll go through isolation, keys, identity, models and deployment with your security team, and answer what this page doesn’t.
- Hosted, dedicated or self-hosted
- Your choice of models, self-hosted too
- Pricing set out in a written proposal