Skip to content

How we work

Etheon builds AI software in six steps, from the first conversation to the next release. Choose a dedicated team, a fixed-scope project or team extension.

How we work. Six steps from the first conversation to the next release: formulate, design, create, test, launch and improve.

Formulate.

What happens

  • The problem and its users, named
  • How success is measured, agreed
  • The data and the risks, listed
Who leads
Etheon, with you
You receive
  • Scope document
  • Success measures
  • Risk list
  • Build plan
Ends when
you approve the scope

Three ways to work with us. Who leads, from us to you.

Dedicated team. A team that works only on your product. You set the priorities; we run the delivery.

What you get

  • A product team sized to the work
  • One accountable lead
  • Weekly demos of working software

Team shape

Dedicated team
A whole product team
Fixed-scope projects
A team sized to the scope
Team extension
Engineers who join your team

Who leads

Dedicated team
Etheon, with you
Fixed-scope projects
Together
Team extension
You, with us

How it is priced

Dedicated team
by team
Fixed-scope projects
by scope
Team extension
by team

Best for

Dedicated team
A product with a long roadmap
Fixed-scope projects
A clear scope and a fixed budget
Team extension
More engineers for a team you already run

What you can count on. Ownership, quality and security on every engagement.

How we work · What you can count on · 1 of 2

You own what we build. The code, the models and the accounts, in your name.

What it is

Ownership is who holds the code, the models and the accounts a project creates. With Etheon it is you: the repository, the cloud accounts and the trained models are in your company's name from the start.

What we do

  • The code in your name
  • The models in your name
  • The accounts in your name

How we do it

  1. Your accounts firstThe repository and the cloud accounts are opened in your company's name, or we work in yours.
  2. Your repository from the first commitEvery change lands where you can see it.
  3. Models in your nameTrained models and their data stay in your accounts.
  4. Hand over the keysAccess, docs and runbooks, with nothing left only in our hands.

Questions

What about open-source parts?

Open-source parts keep their own licences. We list each one in the docs, so your lawyers can check them.

Can the Lab's own code end up in our product?

Where it fits, under the licence its repository states. It is listed in the docs like any other open-source part.

Can another team take over?

Yes. Everything is in your name, so another team can pick it up from the repository and the docs.

What you get

  • The repository
  • The accounts
  • The docs

Related

Tell us your use case and timeline. We reply within one business day.

How we work · What you can count on · 2 of 2

Quality you can check. Every change tested and every model evaluated before release.

What it is

Quality is how you know the software does what it should before your users find out it does not. We test every change, evaluate every model before release and release in stages, so a problem stays small.

What we do

  • Tests in the pipeline
  • Every model evaluated before release
  • Releases in stages, each with a rollback

How we do it

  1. Agree what good meansThe success measures, and the cases a model must get right, written down first.
  2. Test every change automaticallyThe tests run before a person reviews the change, and a failing test stops the merge.
  3. Review every changeA second engineer reads the code before it merges.
  4. Compare every model with the lastA new version runs against the same evaluation set as the one before it.
  5. Release behind a rollbackIn stages, watched, with the previous version one step away.

What you get

  • Test results for every change
  • An evaluation set and its scores
  • Release notes
  • A rollback plan

Stack and tools

  • Test frameworks
  • Continuous integration
  • Code review
  • Evaluation sets
  • Error monitoring

Related

Tell us your use case and timeline. We reply within one business day.

How it starts. Three moves before the first line of code.

  1. A call.

    Tell us your use case and timeline. We reply within one business day.

  2. A written proposal.

    The scope, the team and the plan, in writing.

  3. A first sprint.

    Working software at its end, reviewed with you.

Get started with Etheon

Tell us your use case and timeline. We reply within one business day.

FAQ

Answers on cost, ownership and timelines.

Any questions? Reach out

Trust

How we protect your data and code.

Trust