Bosphorus

Proof of concept — fourteen days

Fourteen days, your hardware, your hardest prompt

Week one — stand it up and connect it. The control plane, nodes that enrol themselves, single sign-on against your identity provider, teams and quotas, and your first users working normally.

Week two — govern it and judge it. Your rulesets, your document corpus, your dashboards, your people using it for real work.

Bring the prompt you are most afraid of. Watching it come back refused, with the correct legal citation, before any model saw it, is the fastest way to understand this product.

What you will see

We do not have logos to show you. We have six things you can check yourself, on your own infrastructure, inside two weeks:

A star count proves popularity. A passed criterion proves fitness, and it is the only kind of proof that goes into a security reviewer’s report.

We are our own first customer

Bosphorus has run our company’s AI in production since July 2026 — the chat workspace, the agent workspace, the editor extension, expense capture from a photograph, and every model call any of them makes. A few hundred people who are not the developers use it every working day, on the same build a proof of concept would give you.

We are not going to pretend that is a reference list. It is something more useful at this stage: a product whose failure modes we have already met.

What a PoC needs from you

A small Kubernetes cluster, one or two GPU or Mac nodes you already own, an identity tenant, and five to twenty pilot users. Everything else ships with the product.