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.
Etheon built Jeriko for a client: a team of personal AI agents on one computer, each a person in the app with its own memory and instructions.

Jeriko is client work. Etheon built it for a client, and we name it here with the client's permission. In its own words, Jeriko is your team of personal AI agents. This note says what that means, in the words Jeriko uses for itself, and where its code can be read.
In Jeriko, each agent is a person in the app. Each one has its own memory, its own instructions, its own wallet and its own email address.
All your agents live on your one computer. They share its desktop, its browser and the apps that you connect.
Jeriko's command-line toolkit is the part whose code is public, so your engineers can read it: Jeriko's toolkit on GitHub (opens in a new tab).
The story of Jeriko is on our Work page, beside Kuest AI's, with the words of a team that used 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.
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.