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.
You do. The code, the models and the accounts are in your name, and the repository is yours from the first commit.
You do. The code, the models and the accounts are in your name, and the repository is yours from the first commit. Ownership is who holds the code, the models and the accounts a project creates.
In four steps, from the first day to the handover:
You receive the repository, the accounts and the docs.
No. Whichever way we work with you, the code, the models and the accounts are yours.
They are yours too. Trained models and their data stay in your accounts. When we fine-tune a model, you receive the tuned weights, in your name where the base model's licence allows. When we train a model for one task, you receive the model and its training code.
Open-source parts keep their own licences. We list each one in the docs, so your lawyers can check them.
Where it fits, under the licence its repository states. It is listed in the docs like any other open-source part.
Yes. Everything is in your name, so another team can pick it up from the repository and the docs. With a startup, we plan for it from the start: a code base you cannot take over is one of the four risks founders bring us, and its answer is your repository, your accounts and docs from day one. A scope document and its build plan are yours too, written so any team can build from them.
We prepare the store listings, submit each release and answer the stores' reviewers, under your own developer accounts.
We never train models on your data without your opt-in. Your data stays isolated from other clients.
Ownership is the first of three things we hold to on every engagement, with quality and security: see How we work and the FAQ. Tell us your use case and timeline. We reply within one business day.
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.