Skip to content
An electronics repair bench: a soldering station, test instruments and hand tools laid out among components.
Built the way a bench is: every part where you can see it.Photo: Wolfgang Stief, CC0 · credits

Built to say where it stops.

Kodela started as the platform a small team built to run its own AI coding agents on its own code, without handing either to someone else.

It still runs that team's work first, and our rule is that enforcement settings (deny-mode egress, auto-run checks) run on our own team for a week before we recommend them to you.

Three principles

Three principles press one to see it hold

claim · and its limit, same line

egress proxy · one way out for every workspace on your host

limit · ships in observe: it logs and lets through until you switch to deny

Part of Uni AI Pro FZC LLC

Kodela is a product of Uni AI Pro FZC LLC, a company that offers professional certifications and courses in AI, data science, cloud, cybersecurity and blockchain.

The company’s own site covers its certifications, membership and learning programmes. Kodela is its platform for developers and their AI helpers; this site covers Kodela only.

The companyUni AI Pro FZC LLC
Name
Uni AI Pro FZC LLC
Address
Business Centre, Sharjah Publishing City Free Zone, Sharjah, United Arab Emirates

What Kodela is, and is not

We would rather lose a sale to a limit you read here than keep one that you discover later.
What Kodela is, and what it is not
IsIs not
Self-hosted workspaces for developers and AI agentsA hosted service
Credential brokers and one controlled exitA VPN or network access product
A record of which pushes an agent wrotePublicly verifiable provenance (yet)
Evidence you can use in an auditA certification
Early, and run by the people who build itA company with a support SLA (yet)

So far

Short, because it is early. No dates we cannot show you.

  1. Built for one teamA platform to run a small team's own AI coding agents on its own code, on its own host.
  2. Run on that team firstIt still runs that team's work. Enforcement settings run there for a week before we recommend them. Pilots are by conversation.
  3. Still openThree decisions: publishing the source (marked soon, not promised), a hosted version (undecided) and live billing (not built).

What shipped, and when, is on the changelog.

What we are not, yet

  • Not open source. The code is proprietary, shared with pilot teams on request.
  • Not certified. No SOC 2, ISO 27001 or other certification is held or in progress.
  • No customer names or quotes. None are published here, and none will be without written permission.
  • No working contact channel yet. The forms on this site are not connected.

Read the wiring

How the pieces fit, and where each one stops.