Ways to partner
Model and infrastructure
You run inference we should be routing to. Providers sit behind one adapter interface, so an integration is a well-scoped piece of work rather than a rewrite — but it is real work, and we prioritise by what our users are asking for. Bring your latency distribution, your cost per unit and your failure modes, not only your benchmark scores.
Studios and agencies
You deliver client work and need the pipeline to hold up under revisions. We work closely with a small number of teams: you get direct access to the people building it, and what breaks for you shapes the roadmap. In exchange we ask for honest reporting of what did not work, which is harder to give than it sounds.
Tools and platforms
You have an editor, an asset library or a DAM our users already live in. The API and the workflow format are the seam. Most of this work lands in import and export, and the useful first question is which direction matters more to your users.
Education and research
You teach or research in this field and need seats, syllabus material or access for a cohort. There is a programme for this and it is not a discount code — tell us the course, the size and the term dates.
What a model integration involves
The most common enquiry, so here is the shape of it before you write.
A conversation about fit
What your model is genuinely better at than what we already route to. "Comparable quality, lower price" is a real answer; "state of the art" without a dimension attached is not.
Adapter work
An adapter maps your API onto one interface: submit, poll or webhook, cancel, and the error taxonomy. The last of those is where the time actually goes — a provider whose timeout looks like a success is what makes a settlement path hard.
Evaluation
We run it against the cases our users actually hit before it appears as an option. This is not a formality and has ended integrations.
Rollout
Behind a flag, to a subset, then generally. Node types gain an option; nothing about existing graphs changes.
- What we need from you
- An API with documented error semantics, a sandbox with quota, a technical contact who can answer within a day during integration, and clarity on rate limits and cost.
- What we do not need
- Exclusivity, co-marketing commitments as a precondition, or a minimum spend to start a conversation.
- What we will ask about
- Data handling — whether prompts and outputs are retained, whether they are used for training, and what a customer can be told about that. If the answer is unclear, the integration stops there.
What to expect from us
Write with specifics
What you do, what you want to connect, and the number that makes it worth doing for you. Vague introductions get vague replies, and a deck without a technical page rarely survives the first call.
A call with someone who builds
Not a funnel. The first call includes whoever would do the integration work, because feasibility is the real question and a salesperson cannot answer it.
A written scope
What each side ships, by when, and what "working" means in a way both parties would recognise. Nothing starts on a handshake and a deck.
A pilot before a contract
Where the shape allows it, we would rather run something small and real than sign something large and theoretical. A pilot that fails is information; a signed agreement that quietly goes nowhere is not.
Common questions
Is there a formal partner tier structure?
No, and inventing one at this size would be theatre. What exists is a small set of working relationships with real scopes. If a tier structure would help you internally, say so and we will write something that fits.
Do you do revenue share with tool platforms?
It depends on the shape. Where an integration drives usage that is attributable, yes, and the terms are written before work starts rather than negotiated after it succeeds.
Can we resell Nova Studio to our clients?
Talk to us. Agencies delivering client work on the platform is a normal case; a white-labelled resale is a different conversation with different support obligations.
We are a model provider but very early. Is it worth writing?
Yes, if you are better at something specific. The adapter layer exists precisely so that a specialised model is not disadvantaged against a general one.
Do you sign NDAs?
Yes, before any conversation where you need to describe something unreleased. Send yours or ask for ours.