For larger organisations: what exists today, and what does not.
Kodela runs on your hardware, keeps your credentials on your host and writes a record you can hand an auditor. It is also early. This page lists both halves, so you can decide in one read whether a pilot makes sense.
Showing all 38 rows
| Enterprise need | Kodela today | Status |
|---|---|---|
| Available · 15 | ||
| Partial · 6 | ||
| Pilot only · 4 | ||
| Not currently available · 11 | ||
| Other · 2 | ||
| Enterprise overview | Self-hosted workspaces with governance for AI agents | Available |
| Enterprise security | Host-held credentials, per-organisation networks, fail-closed firewall, hash-chained audit | Available (egress starts in observe) |
| Enterprise administration | Operator console; per-organisation console; four roles including a read-only auditor | Available |
| Enterprise deployment | Single Linux host; workspaces may also run on members’ own computers if your organisation turns it on (see Device management) | Available |
| Enterprise self-hosting | The only deployment model | Available |
| Enterprise cloud (managed) | None | NOT CURRENTLY AVAILABLE |
| Private cloud / your VPC | Runs on any Linux VM you control that meets the requirements; not tested per provider | Available as self-hosting; per-cloud guides are not written |
| Air-gapped environments | Pinned and checksummed components; manual image transfer; offline scanners | PARTIAL: no offline bundle |
| High availability | None | NOT CURRENTLY AVAILABLE |
| Scalability | One host; multi-host placement built and off | PARTIAL: no published capacity figure |
| Identity integration | OIDC per organisation: Entra ID, Google Workspace, generic | Available (never tested against a real IdP on record) |
| SSO | As above | Available, with the same caveat |
| SCIM | None | NOT CURRENTLY AVAILABLE |
| SAML | None | NOT CURRENTLY AVAILABLE |
| MFA | Enforced through your IdP on SSO logins | PARTIAL: no native MFA |
| RBAC | Owner, admin, member, auditor; per-member grants; operator floors | Available |
| Audit logging | Hash-chained, eight streams, 90-day default retention. An organisation Audit dashboard for owners, admins and auditors: timeline, refused counts, integrity panel and an export that is itself audited; up to 90 days, never past your retention, only records provably the organisation’s own. An AI usage dashboard: requests, tokens and cost, with no spend cap, cost only where the cost meter is on, and AI tools that hold their own login inside a workspace not measured. Password and shared-credential sign-ins are recorded from orxy V1.7.2.2 on | Available |
| SIEM integrations | CEF, LEEF, syslog, JSON, CSV export | PARTIAL: export, not forwarding |
| Policy management | Security levels, strictest-wins scopes, more than 140 settings | Available |
| Device management | Members’ own computers can host their workspaces: off by default; an operator grants it and the organisation turns it on. The agent updates itself, access lapses after 30 days without a connection, removing a computer revokes its key at once, and offboarding archives its workspaces. There, egress is observed, not enforced, DNS filtering is not enforced, the source is readable on the disk, and Docker is not available | PARTIAL: off by default; tested end to end only on Windows (Linux laptops up to enrolment, Mac only in a simulation) |
| Compliance | Evidence report mapped to ISO 27001, SOC 2, NIST 800-53 | Evidence only; not certified |
| Data residency | Wherever your host is (and members’ own computers, if turned on) | Available (you decide) |
| Data control | Code, audit and chat on your host (code also on a member’s own computer, if turned on); model calls go directly to your provider | Available |
| Backup / recovery | Encrypted backup with partial restore | Available; not scheduled by default |
| Disaster recovery | No runbook, no replica | NOT CURRENTLY AVAILABLE |
| Support | Direct access to the builders during a pilot | Pilot only; no SLA |
| SLAs | None | NOT CURRENTLY AVAILABLE |
| Professional services | Host bring-up help during a pilot | Pilot only |
| Implementation | Guided bring-up | Pilot only |
| Migration | Not applicable (no incumbent product to migrate from); workspace setup from devcontainer startup tasks | Partial |
| Training | None formal | NOT CURRENTLY AVAILABLE |
| Customer success / TAM | None | NOT CURRENTLY AVAILABLE |
| Custom integrations | By pilot agreement | Case by case |
| Custom contracts, MSA, DPA | None published | NOT CURRENTLY AVAILABLE |
| Procurement | No billing entity process published | NOT CURRENTLY AVAILABLE |
| Security questionnaires | Answered by the builders during a pilot | Pilot only |
| Enterprise onboarding | Invite-only; the first operator is created from the command line | Available |
| Organisation deletion | None | NOT CURRENTLY AVAILABLE |
Why self-hosting matters here
Your source code, your audit trail and your agents' outbound traffic stay on infrastructure you control. If you turn on members’ own computers as workspace hosts, the source of those workspaces sits on that computer’s disk, and its outbound traffic is observed, not enforced. Model calls go from your host to your provider under your contract. Kodela, the company, is not in the data path.
If the company disappeared, the software would keep running on your host. It depends on no Kodela service, and pilot teams have the source.
- Source code
- Workspace volumes on your host; a member’s own computer, if turned on
- Audit trail
- On your host's disk; 90 days by default, raise-only
- Control store
- One file on your host
- Model calls
- Your host to your provider
- Telemetry
- None sent to Kodela
How a pilot works
It replaces "contact sales". There are no customer stories yet: pilots are how that evidence will be gathered.
- Bring up a hostWe help you bring up one host on your hardware.
- Run real workYour team works in it on real repositories.
- Meet weeklyWe fix what blocks you first.
- Tell us what brokeWhat failed, what was missing, what blocked a yes. It sets what we build next.
Pilot terms, including any fee, are agreed individually. Nothing is billed today.
What we will build when a deal needs it
If one of these blocks you, say which: it decides what we build next.
Tell us which one- High availabilitynot built
- SAMLnot built
- SCIMnot built
- A Postgres control planenot built
- Customer-managed keysnot built
- A support SLAnot offered
Procurement readiness
What a procurement team usually asks for, and where each item stands.
| Item | Status |
|---|---|
| W-9, VAT registration, company details | Not published yet |
| Standard MSA or order form | Not published |
| DPA | Not published Kodela runs on your host and has no hosted service. |
| Subprocessor list | Not applicable There is no hosted service. |
| Security questionnaire (SIG Lite, CAIQ) | Answered in the pilot Not pre-filled. |
| Penetration test report | None |
| Insurance certificates | Not published yet |
| Source code escrow | Not offered |
Questions from larger teams
Do you support SSO?
Yes: OIDC per organisation with Microsoft Entra ID, Google Workspace or a generic provider. It has not yet been tested against a customer's live IdP.
SAML? SCIM?
Not today.
Is there an SLA?
No. During a pilot, the people who build it support it. There is no support contract or SLA yet.
Can we run it in an isolated environment?
Partly. Components are pinned and checksummed, images can be moved by hand, and the workspace scanners run offline. There is no offline installer bundle yet, and model calls need a route to your provider.
What happens during an outage?
It is one host with no high availability. If the host is down, workspaces are down. If the egress proxy is down, the firewall blocks outbound traffic rather than allowing it. Encrypted backups restore per organisation or per workspace.
How does enterprise licensing work?
There is no enterprise licence yet. The code is proprietary, all rights reserved, and shared with pilot teams on request.
Are you SOC 2 certified?
No. Kodela produces an evidence report mapped to SOC 2, ISO 27001 and NIST 800-53 controls that you can use in your own audit.
What it does not do yet
The rows marked not currently available, in one place.
- No high availability or disaster recovery. One host, no replica, no restore runbook.
- No SAML or SCIM. OIDC per organisation is what exists.
- No managed cloud. Self-hosting is the only model.
- No SLA, training or customer success team. Support is the builders, during a pilot.
- No published contracts or procurement process. No MSA, DPA or billing entity process yet.
- No organisation deletion. Not currently available.
Decide in one read, then pilot
If the table works for you, talk to us about a pilot. Read the security model first if you want the detail.