We bill a flat monthly licence per hub. Nothing else. €990 per hub per month — no per-seat pricing, no hourly or session pricing, no volume discount, no tiers. The licence runs from contract start until cancelled; we don't track individual deployment days. On days the hub is not deployed, your cloud costs are lower — but the software & support fee does not change.

The single Hub Owner per hub gets full support: SSO/OIDC, redeploys, incidents, DPA on request, and everything else that touches running the hub. The only carve-out is changes to the cloud-init modules (terraform-cloudinit-*) for your specific use case — those are consulting work, billed separately on request. Heuristic: if the work touches terraform-cloudinit-* for you, it's consulting; otherwise it's included.

Flexpair is not a remote desktop per seat. It is one shared workspace that the whole team inhabits at once — one cursor, one screen, one running environment. The right analogy is a conference room, not an office chair: you rent it for the months you use it, and the price covers the whole group. At three to five people sharing a hub, that is €198–€330 per person per month — in the range of standard per-seat tooling subscriptions. Per-seat pricing would contradict the product.

Each hub runs its own infrastructure pipeline with a forced full redeploy at the latest every ~90 days when the wildcard TLS certificate rotates. That reset eliminates any economy-of-scale window we could pass on. The monthly licence is a flat fee regardless of contract length.

One one-time fee: €2,490 auth setup per cloud account. It covers the Terraform OIDC trust for credential-free deployment and your corporate IdP connection for user login, and is shared across all hubs in that account. A new cloud account triggers a new fee. There is no per-hub setup fee — each additional hub in the same account starts at the monthly licence with no setup charge.

The minimum term is one month. After the first month, you can cancel at any time. There is no sub-monthly billing — we don't sell hours, days, or sessions.

No. The monthly licence is the smallest unit. The persistence story — open terminals, running jobs, editor state surviving across reconnects — works best with an always-available workspace; hours and sessions undermine that promise.

It is included — guided sales demos are on us. They are not a product sale.

Flexpair is early. As long as the founder can personally white-glove every customer, we deliberately ship a single offer. Whatever your size, you get the kind of attention an enterprise vendor would charge a separate tier for. Tiering is a problem for the day we have too many customers to keep that promise — not before.

Today, no — one hub, one price, regardless of how many desktops are inside it. We may revisit this once we have enough billing data to see whether very large hubs systematically generate disproportionate cost. Until then, the simplicity of one number wins.

Each hub has exactly one named Hub Owner on your side, and that person is the sole interface to us. End users (admin / editor / watcher roles) collaborate inside the hub but never contact Flexpair directly — they go through the Hub Owner. This keeps the personal-attention promise sustainable.

No — that's the €2,490 auth setup fee per cloud account (see pricing). It's a one-time deliverable, not a recurring support item. It covers both the Terraform OIDC trust (so HCP Terraform can deploy without static cloud credentials) and your corporate IdP connection for user login. The fee is shared across all hubs in that cloud account. A new cloud account triggers a new €2,490 fee. Day-to-day IdP work — role mapping, group membership, user provisioning, password resets — happens on your side, inside your IdP. We map IdP groups 1:1 onto the admin / editor / watcher roles, and that contract is fixed.

Yes, on request. Your data stays in your own cloud account — Flexpair never hosts it and has no standing access to your VMs. The deployment is fully provisioner-free (cloud-init only), so there is no SSH session into your infrastructure during normal operation. A DPA is available for customers who need it for their own compliance process.

Yes. Coordinating and running the redeploy is part of operating the hub. Persistent volumes carry your state across.

Anything that requires editing the cloud-init modules (terraform-cloudinit-hubconfig, terraform-cloudinit-satconfig) for your specific environment: extra packages baked into the desktop image, custom startup scripts, custom tooling on the gateway, anything that changes what the VMs become at first boot. That work is consulting, billed separately, on request.

Because cloud-init changes are bespoke engineering against your environment, not operations on a shared product. Bundling them into a flat monthly licence would either subsidise heavy users at the expense of light ones, or force us to invent tiers — which we deliberately don't have. Treating it as consulting keeps the monthly licence price honest.

On request. The list-price floor is the prevailing DACH senior DevOps day rate (typically €1,200–€1,800 per day). We scope the work, agree on it in writing, and invoice separately from the monthly licence. It will appear on your offer as “Cloud-init customisation — on request, billed separately”.

Yours. Flexpair is BYOC (Bring Your Own Cloud). We deploy a hub into your cloud account via Terraform — there is no Flexpair-hosted offering. Your data stays on your VMs, in your network, under your contracts.

AWS is the first shipped implementation. The architecture is provider-agnostic — any cloud whose Terraform compute provider accepts a cloud-init/user-data payload at VM creation is eligible. The current shortlist with details is on the Compatible clouds page. Our next concrete port is OVHcloud via the OpenStack-compatible API.

No. Cloud compute, storage, and egress are billed directly by your cloud provider on your account. Use your provider's own pricing calculator for those numbers — they know their SKUs better than we do. The €990 monthly licence is purely the Flexpair software & support fee.

OIDC Federation with HCP Terraform is preferred over static cloud access keys. This is covered by the one-time €2,490 auth setup fee per cloud account, which also includes the corporate IdP connection for user login.

A hub is one gateway VM (public IP, terminates TLS, runs Guacamole + Mumble + the browser Mumble client) plus N persistent desktop VMs (no public IP, connected to the gateway through SSH tunnels). One hub serves many users; the cursor is shared across all users on a given desktop.

Yes. All participants on the same desktop control one mouse pointer (enforced at the VNC level via x11vnc shared mode on the X11 screen). It is not multiple cursors with awareness; it is one cursor. Practical limit per desktop: 2–3 active drivers, watchers nearly unlimited.

No, by design. Audio only, via always-on Mumble. Audio-only focuses attention on the shared desktop instead of faces, removes the bandwidth competition with the VNC stream, and avoids appearance bias.

Yes. EC2 (or equivalent) instances run permanently until explicitly destroyed. Open terminals, running jobs, editor state — everything persists across sessions and reconnects.

Flexpair runs on a wildcard TLS certificate from Let's Encrypt for *.flexpair.app, valid 90 days. Before expiry, the pipeline rolls a fresh hub and persistent volumes carry your state across. So you typically get 30 to 90 days of continuous uptime per deploy, depending on where DNSimple is in its renewal cycle when you apply.

No. Browser only. Teammates log in via your identity provider and step into a desktop.

Book a call. We talk through your environment, agree on scope and identity provider, and run the first deploy together. The OIDC + first-hub setup is the €1,990 anchor; ongoing usage is the monthly licence.

Yes. A red-team engagement, a training cohort, a hackathon — you can start with a single monthly licence and cancel when the engagement ends. The monthly rate is the same regardless of how long you run.

What is yours stays yours: the data inside your VMs, in your cloud account, under your contracts. You can extract it before teardown via the standard mechanisms (snapshots, volume exports, SFTP from the upload share). The Flexpair Terraform configuration, modules, and Stack state are not part of the handover — those are our product. There is no proprietary data lock-in, because your data was never on our side to begin with.