Enterprise / 04
Your boundary. Our switchboard.
Every Thinker customer is Enterprise. KYC and a contract come first. Calls stay private through the EU ingress, a tunnel or a firewall lock; both models share one OpenAI-compatible API and EUR ledger.
- Plan
- Enterprise only
- First reply
- ≤ 3 business days
- Region
- EU only
01 / Connectivity
Choose the private path.
All of it is Enterprise and KYC-gated. Add a tunnel or firewall lock without changing the API contract.
Private route
The standard path: HTTPS to our EU ingress, then a private network to an isolated model pool. No GPU host has a public model port.
Private tunnel
WireGuard or IPsec from your VPC or office to your inference endpoint. The address plan and failover path are agreed before activation.
Firewall lock
Pin calls to an agreed set of static egress addresses, with optional mutual TLS. Rules and address changes are exchanged before cutover.
02 / Commitments
Procurement is part of the product.
A security questionnaire should not take six weeks. We keep the answers current and the documents ready before the first call.
- SSO and SCIM · roadmap
- OIDC or SAML single sign-on and SCIM 2.0 are contracted roadmap items. Password plus TOTP is available today, including break-glass staff access.
- KYC/KYB and invoicing
- Identity and entity checks, VAT validation, purchase-order references and net terms. Invoice billing with an explicit credit limit.
- DPA and subprocessors
- A signed Art. 28 DPA with SCCs, a named subprocessor list, 30-day change notice and audit co-operation.
- Named reliability contact
- A shared incident channel, monthly reliability review and direct escalation to the operator on call.
03 / Start
Tell us what you are building.
A solutions engineer reads every inquiry. Include a security questionnaire in your reply and we will work from it rather than starting over.
- 01
Triage
We check fit, region and private-path requirement within one business day.
- 02
Technical call
Connectivity, identity, volume and data-flow review with an engineer.
- 03
Written scope
Private-path plan, DPA, subprocessors and a fixed commercial proposal.
Common questions
Can we connect over a private network?
Yes, by agreement. Use a WireGuard or IPsec tunnel, or pin the endpoint to your firewall and optional mTLS. Inference still uses the same OpenAI-compatible API; only the path changes.
Can inference run in our VPC?
Yes on a private deployment. We install the same hardened stack in your EU datacentre and hand over the runbook. There is no vendor control plane.
Do you support SSO?
Not yet. Password plus TOTP is available today; OIDC/SAML SSO and SCIM 2.0 are roadmap items for contracted customers.
What capacity is available?
A reserved pool is sized from a short traffic model during the technical call. Capacity is held before the contract starts.
How is billing handled?
EUR invoice after KYC and contract, with net terms and an explicit credit limit. Committed prepaid credit remains available.
Not ready for a call?
Apply, complete KYC and contract, then choose the private path. The API does not change.