Runs on your machines
Models and workflows live on a VM or server you control. Your cloud account or the box in the office — not a product we rent back to you.
Build My Workflow
Most of what we build runs on hardware you control. Prompts and files stay on your network. You pay us once to design and hand it off — not a vendor per token, per seat, or per leaked document.
The problem
Chat demos look cheap until usage scales. Token charges and seat licenses are the obvious cost. The quieter one is every prompt leaving the building into a vendor tenancy you do not control. We default to self-hosted models so the meter stays off and the data stays yours.
The stance
Models and workflows live on a VM or server you control. Your cloud account or the box in the office — not a product we rent back to you.
Prompts, files, and logs stay inside your network. You set who can reach the model. A third-party tenancy is not in the path unless you choose it.
Inference is yours after handoff. We are not reselling an API with a markup you will feel every month.
Adding a colleague should not open a new invoice. The system is yours, not a seat-licensed product.
How it works
We start with the process you already run — tools, handoffs, and the points where time disappears.
One production path on infrastructure you host, wired to your systems, with clear ownership and a way to see if it is working.
Docs, a walkthrough, and a short support window so your team can run it without us in the loop.
Packages
Free
30 min call: goals, tools, go / no-go.
$1,200
Map the current process and 3–5 automation opportunities.
$3,500
One production workflow, integrations, docs, 2-week support.
FAQ
No. We design and build a system you host. You own the result. We are not a SaaS product and we do not put you on a token plan.
It is more private by default: prompts are not sitting in a vendor’s multi-tenant cloud, and you decide who can reach the model. You still have to patch the box and lock down access — we set that up and show you how. Vendor cloud is the exception, not the offer.
No. Self-hosted means it runs on hardware you control, not that it is air-gapped. Your team can reach it on-prem. Vendor cloud is the exception, and we say so on the discovery call.
Open-source models, your VM or on-prem box, and the tools you already run. Automation platforms and APIs when they earn a place. We do not start from a vendor list.
Most single-workflow projects land in a few weeks after discovery, depending on access to systems and how clear the process is. The audit is shorter. Suites take longer.
Thirty minutes: the work you want off someone’s plate, whether it can run self-hosted, and a go / no-go. If there is no fit, we say so.
No. If you move forward to a Single workflow or Operations suite, the $1,200 audit fee is applied as a deposit against that build. You still get the written brief either way — it is only extra cost if you stop after the audit.
Basic support is $250 / month for light bug fixes on workflows we already built and handed off. Monthly partner is $2,500 / month if you want new work, monitoring, and small changes on an ongoing basis.