How we build
Built in your accounts. Run on your keys. Handed over whole.
This page is for whoever has to sign it off technically. The rest of the site says what we do and why; this says where it runs, whose model, whose keys, who approves what, and exactly what you are holding when we leave.
The shape of a build
One loop, inside a system you already own.
Every workflow we build has the same five parts. The boxes change — your CRM, your model, your rules — but the loop and where it lives do not.
The rules
Your account, your keys, your choice.
We do not have a stack to sell you. What we hold to is where things run and who owns them — the six things below are true of every engagement, whatever the tools.
01 · Where it runs
In your accounts. Nothing routes through us.
The workflow lives in your cloud or SaaS tenancy — the CRM, the inbox, the helpdesk, the spreadsheet the work already happens in. There is no Binarify proxy, no middleware we host, no proprietary layer between you and your own system. If Binarify disappeared tomorrow, it would keep running.
02 · Whose model
Whichever provider you prefer.
Our own systems run on Anthropic under its commercial terms, which do not use the data for training. If your cloud already licenses a model — Azure OpenAI, AWS Bedrock, Google Vertex — we build on that, so the data never leaves a tenancy you already govern. The choice is yours and we will tell you plainly what each one costs.
03 · Whose keys
Always yours. Never a shared Binarify key.
Inference runs under your API key or your cloud account, without exception. Usage, billing and data-handling terms are between you and the provider, visible in your own console, and they stay exactly as they are when we leave.
04 · What we integrate with
Whatever you already run.
CRM, helpdesk, inbox, calendar, accounting, spreadsheets, the internal tool someone built in 2019 — through their APIs. If you already use an orchestrator such as n8n or Make, we work inside it rather than around it. We do not have a stack to sell you; the stack is the one you have.
05 · Access
Least privilege, in your tenancy, revoked at handover.
Named service accounts with only the permissions the workflow needs. Credentials live in your secret store, never on our machines. Every access we were given is revoked or transferred to you when the engagement ends — and the handover pack lists each one so you can check.
06 · Approval and audit
A human where it matters. A log everywhere.
Where a step touches a customer or moves money, we recommend a human approval and build it in unless you decide otherwise — decided with you, per workflow, not assumed. Every automated step is logged inside your systems, so a wrong answer can be traced back to what the model saw and what it did.
What you are holding when we leave
Complete documentation. On everything.
Handover is not a call and a goodbye. It is a pack your own engineers can run the system from, or hand to someone else to run — and it is written so that the day-90 number can be taken again by someone who was never in the room.
// the handover pack
What we will not do
Five things we will never do.
Each of these is checkable in your own console or your own logs. That is the point of writing them down.
- Never use a shared or Binarify-owned API key for your workload.
- Never route your data through a server we run.
- Never leave a proprietary layer you have to keep paying for.
- Never keep an access you gave us after the engagement ends.
- Never put a customer-facing or money-moving step live without agreeing the approval point with you first.
Bring your head of engineering to the call.
Thirty minutes, no deck. Tell us what you run and who would have to sign it off, and we will say what we would build, where it would live, and what they would be handed at the end.
Book a 30-minute callNo sales deck. No follow-up sequence.