Native or cross-platform? Three questions decide it
Deep device features point to native; one team and a close store date point to cross-platform; otherwise either fits, and we talk it through.
Before you sign, check what the firm has built, read its code, see what it holds, ask about your data and ownership, and know who reads your brief.
Before you sign, you can check what the firm has built, whether your engineers can read its code, what it holds, what happens to your data, who owns the result, how it tests a model and who reads your brief. Here is where to check each with Etheon.
Yes. Our Lab's own product is Etheon Delta. We built Jeriko and Kuest AI for clients, and we name both with each client's permission: Jeriko is a team of personal AI agents, and Kuest AI is an AI tutor that teaches step by step. Their stories are on Work.
Yes. Our open-source code is on GitHub. You can use it under the licence each repository states: the code is public for your engineers to read, run and build on.
We hold SOC 2 Type II, ISO 27001 and CSA STAR. Your security reviewers can ask for the SOC 2 Type II report under NDA, with the rest of the evidence:
Document | How to get it |
|---|---|
SOC 2 Type II report | Under NDA, on request |
ISO 27001 certificate | Public |
CSA STAR | Public |
Security brief | On request |
The whole evidence pack is on our Enterprises page.
We never train models on your data without your opt-in. Your data stays isolated from other clients. It is stored in the region you choose, and your data and its backups stay there.
You do. The code, the models and the accounts are in your name, and the repository is yours from the first commit. The answer is on our FAQ.
Every model we build passes the same gates before it reaches your users: task quality, grounding, safety, privacy, latency, cost and drift. We agree each threshold with you before work starts, and a release candidate that misses one waits until it passes. The gates are on our AI page, and our research note How we test a model before release sets out each one.
Yes. Say so in your brief, and we sign an NDA before you share anything confidential.
A partner reads every brief, not a form queue. We reply within one business day.
Four of these you can check on our homepage, under Why Etheon. Tell us your use case and timeline.
Deep device features point to native; one team and a close store date point to cross-platform; otherwise either fits, and we talk it through.
A dedicated team fits a long roadmap, team extension a team you already run, and a fixed-scope project a clear scope, a fixed budget and a date to meet.
Migration moves your systems off your own servers to the cloud you choose, in planned waves, each workload with a rollback point.