Pricing · one fixed price · no surprise line items

One build, one fixed price. From £2,000 to £10,000, plus £40 to £900 a month in your own environment (or no monthly fee if you deploy on existing on-premises infrastructure).

No phases to climb, no separate invoices to approve. You pick the tier that fits, we quote one fixed number on a free scoping call, and you own the code from day one. Introductory launch pricing while the studio builds its case-study base, these rates are locked in for your engagement and rise after 30 September 2026.

Book a free scoping call How the build works
One fixed price

Pick the tier that fits. That's the price.

No phase ladder, no quote-on-a-quote. Three tiers, one all-in fixed fee each. Where you land depends on integration count, compliance burden, and how much load runs through the system after launch. The run cost is the only separate item, and it sits in your own environment, not on a Zyvra invoice.

Essential

£2,000

Introductory rate · rises after 30 Sep 2026

A single-task build, end to end. One read-only integration, one environment, single cloud region, not in a regulated sector, standard auth.

What's included

  • Scoping, recommended architecture, and a 3-month cost model
  • The working build, deployed in one environment
  • One read-only integration with a production system
  • Code, IaC, and runbook, yours from day one
  • 60 days of bug-fix support (minor tuning, not new work)
Run cost £40 to £80 / month, in your own environment
Standard Most builds

£5,000

Introductory rate · rises after 30 Sep 2026

A multi-step workflow across two or three production systems. Some compliance considerations, moderate load, audit-logging baseline included.

Everything in Essential, plus

  • 2 to 3 integrations, single cloud
  • Audit-logging baseline from the first request
  • Cost tracked against the model for the first three months
  • Custom auth or network policies where needed
Run cost £150 to £400 / month, in your own environment
Regulated

£10,000

Introductory rate · rises after 30 Sep 2026

A regulated-sector starter (FCA, MHRA, ICO) with Article 12 logging and a formal external review run by your compliance team or an external auditor. Multi-system or audit-heavy programmes are quoted above tier.

Everything in Standard, plus

  • Article 12 compatible decision logging from day one
  • Full evidence pack for your compliance team
  • Support for one external auditor review
  • One write-path or multi-region integration where needed
Run cost £300 to £900 / month, in your own environment
Introductory launch pricing

These are introductory rates while the studio builds its case-study base. They're locked in for your engagement and rise after 30 September 2026.

What determines your tier

Three honest drivers move you between Essential, Standard, and Regulated.

No hidden formula. We confirm which tier you're in on the free scoping call, then quote the single fixed number.

Driver · Integrations

How many systems it touches.

Toward Essential (£2K)

  • One AI capability or single task in scope
  • One read-only integration
  • Standard auth (your existing IdP)

Toward Regulated (£10K)

  • Two or three integrations, or a write path
  • Custom auth or network policies
  • Cross-region or multi-cloud constraints
Driver · Compliance

How much the regulator is watching.

Toward Essential (£2K)

  • No regulated-sector overlay
  • Standard data-handling controls
  • No external review needed

Toward Regulated (£10K)

  • Named regulator (FCA, MHRA, ICO, etc.)
  • Article 12 logging from day one
  • Full evidence pack plus external auditor review
Driver · Load & ops

How hard it runs after launch.

Toward Essential (£2K)

  • Single-task automation, light volume
  • Single environment, one region
  • Standard monitoring

Toward Regulated (£10K)

  • Multi-step workflow, higher volume
  • Multi-region or multi-account
  • Full observability and decision logging
Scope per tier

What the fixed price includes, and what starts a new SOW.

Fixed price means fixed scope, not unlimited scope. Each tier has hard limits, named below. Anything past them is a fixed-fee SOW amendment, agreed before any new work starts, never a surprise on the invoice.

Essential · £2,000

Single-task build.

Included (the limits)

  • 1 read-only integration
  • 1 deployment environment, 1 cloud region
  • Standard auth (your existing IdP)
  • 1 handover session
  • 60 days of bug-fix support

New SOW if you need

  • A second integration, or any write path
  • A second environment or region
  • Regulated-sector logging or evidence
  • New features after handover
Standard · £5,000

Multi-step workflow.

Included (the limits)

  • Up to 3 integrations, single cloud
  • Audit-logging baseline
  • Custom auth or network policies
  • Up to 2 handover sessions
  • 60 days of bug-fix support

New SOW if you need

  • A fourth-plus integration, or multi-cloud
  • A regulated evidence pack or external-audit support
  • Additional workflows beyond the scoped one
  • New features after handover
Regulated · £10,000 · starter

Regulated deployment starter.

Included (the limits)

  • Everything in Standard
  • Article 12 logging + evidence pack
  • One external auditor review supported
  • One write-path or multi-region integration
  • 60 days of bug-fix support

Quoted above tier

  • Multi-system or multi-country programmes
  • Repeated auditor cycles or heavy remediation
  • Ongoing compliance retainer
  • New features after handover
What "support" means

The 60-day window covers bug fixes and minor tuning to the delivered scope, with a two business-day response target. It is not a retainer: new features, new integrations, new environments, or scope changes are a separate fixed-fee SOW. Ongoing support beyond 60 days is an optional retainer, priced per quarter.

What's in, what's not

The line items that catch people out, called out up front.

Never extra (included in the engagement fee)
  • Discovery and scoping calls before the proposal
  • NDA on request, signed before the first technical conversation
  • The scoping assessment, recommended architecture, and 3-month cost model
  • All design, engineering, and integration work named in the SOW
  • Documentation, runbooks, and the evidence pack for your compliance team at handover
  • 60 days of post-launch support: bug fixes and minor tuning to the delivered scope (not new features or integrations)
  • The repository, IaC, and operational artefacts (all yours from day one)
Extra (paid by you, separately, in your own accounts)
  • Your run cost: your own cloud account with any major provider (AWS, GCP, Azure, or another), or your existing on-premises infrastructure cost. Modelled during scoping for the first 3 months
  • Third-party AI API costs (LLM inference, embeddings) billed by the provider to your account
  • External compliance auditors or legal counsel, if you choose to engage them
  • Integration work for systems added after the SOW is signed (new SOW, fixed fee)
  • New features, integrations, or environments after handover (new SOW)
  • Optional retainer for ongoing support beyond the 60-day window
  • Material scope changes during the build (handled as a SOW amendment with a fixed fee)
Worked example

Mid-size fintech automates KYC document review.

A 600-person UK fintech wants to automate the first-pass review of customer onboarding documents (proof of address, ID, source of funds). Currently a 4-person team spends a day each on the queue. AI-assisted review needs to handle UK GDPR cleanly and produce records the FCA can audit.

The tier: Regulated, £10,000. A named regulator (FCA), Article 12 compatible logging on every flag, WORM storage for decision records, and a documented human-review step put this squarely in the Regulated tier. One fixed price, agreed after a free scoping call.

What the £10,000 covers, end to end. Scoping of the document store, the OCR vendor already in use, the customer-facing portal, and the compliance team's evidence requirements, with a recommended architecture and 3-month cost model. The build, integrated read-only with the existing OCR vendor and document store, validated against 200 anonymised historical cases with decision logging from the first request. Then live in the fintech's own AWS account in eu-west-2: monitoring routed to the existing on-call rotation, WORM storage configured, and the evidence pack handed to the compliance lead.

The early checkpoint. In week one, if scoping had surfaced a blocker, either side could have stopped with a clean pro-rata exit. It didn't; the build went ahead.

Total engagement: £10,000. Plus run cost averaging £280 a month on the fintech's AWS bill (inference, retrieval, WORM storage, logging). Plus the LLM provider's API fees, also on the fintech's account, modelled at £400 to £600 a month at projected volume. The 60-day support window covers the first month of live usage, including the fintech's first internal audit of the new system (run by their own compliance team, not by Zyvra).

The fintech walks away owning the code, the IaC, the runbooks, and the evidence pack. They are the compliance owner and the audit relationship is theirs. Zyvra has zero access after the support window closes.

Pricing FAQ

The questions buyers ask before they sign anything.

How is the price fixed?
On a free scoping call we walk through the three drivers (integration count, compliance burden, and load) and confirm which tier you're in: Essential (£2,000), Standard (£5,000), or Regulated (£10,000). That tier is the price, fixed in the SOW before any work starts. No ranges to negotiate, no "it depends" after you've signed.
Why introductory pricing? Will it last?
These are deliberately low launch rates while the studio builds its public case-study base, early clients get the work at a fraction of what equivalent enterprise engagements cost, in exchange for being early. The rate you book at is locked in for your engagement. Published rates rise after 30 September 2026.
What if it turns out not to be feasible?
The scoping call is free, so a clear "this won't work" costs you nothing. If a blocker only surfaces once the build starts, there's an early feasibility checkpoint in the first week where either side can stop with a clean pro-rata exit, you pay only for the work done, and you keep everything produced so far. About one in four projects turns up a no or a conditional yes with material work needed before it's the right move.
What if the project goes over scope mid-build?
A SOW amendment, fixed fee, agreed before any work on the new scope starts. No retroactive bills, no "actually it cost more than we said". If new scope means the original tier no longer fits, that conversation happens openly and you can decide whether to amend, descope, or stop.
What's the cloud bill, really?
It lives in your chosen environment from go-live. If you go cloud, the bill sits in your own provider account (AWS, GCP, Azure, or another); if you go on-premises, the cost is absorbed into your existing infrastructure spend. Scoping produces a 3-month model with the line items called out (compute, storage, networking, model inference, retrieval, monitoring) for whichever path you pick. For the first three months in production, actuals are reported weekly against that model. Typical brackets for cloud deployments: £40 to £80 a month for single-task automation (Essential), £150 to £400 for full workflows (Standard), £300 to £900 with audit logging and compliance controls (Regulated). On-premises figures depend on your existing capacity utilisation.
What about LLM API costs?
Billed by the provider (Anthropic, OpenAI, Voyage, etc.) directly to your account. Scoping models projected volume; the build reports actuals from the first request. Per-user, per-tenant, and per-day caps are built in so a single request can't surprise your finance team. Typical: a few pence per request, totals depend entirely on your call volume.
Is there a retainer or ongoing fee after the 60-day window?
Only if you want one. The 60-day window covers bug fixes and minor tuning to the delivered scope, with a two business-day response target, it's support, not a standing retainer, so new features or integrations are a separate SOW. After 60 days it's a clean exit: the system is fully yours to run, modify, or hand to another engineer. Optional retainers exist for ongoing tuning, eval-set maintenance, or compliance support, priced per quarter and easy to cancel.
How do you handle a deposit and payment schedule?
Builds up to £3,000 are invoiced in full on kickoff. Above that, the fee splits into kickoff (50%) and handover (50%) instalments. Payment terms: 14 days net, BACS or wire. All fees in GBP excluding VAT. No long contracts: one SOW for the build.
Do you ever quote outside these tiers?
Rarely. The Audit Ledger is a productised offering with its own fixed price (£10,000, deployed or hosted). For genuinely larger engagements (multi-system, multi-country, multi-quarter), we'll quote based on the work needed and tell you up front that we're above the standard tiers so you can decide whether to proceed.
Is Zyvra Studio SOC 2 audited? What's your compliance posture?

No. Zyvra Studio Ltd is a one-person engineering studio and doesn't carry a SOC 2 audit or any similar vendor-level certification. The trust model is different by design.

Everything we build runs in your chosen environment. When that's a cloud (AWS, GCP, Azure, or another major provider), those platforms hold the infrastructure certifications you need (SOC 2 Type II, ISO 27001, and sector-specific schemes like HIPAA, PCI DSS, or FedRAMP, depending on cloud and region) for the layer underneath your application. When that's on-premises or your own private cloud, your existing internal IT controls and audits cover the same ground. Either way, your data never touches Zyvra's systems, because there are no Zyvra systems in the data path. The repository, the deployment, the logs, and the data all live in your environment.

The compliance attestation, the audit relationship, and the regulatory accountability are yours. Zyvra is the engineer who builds the system; you are the organisation that operates and attests to it. The technical capability we build (decision logging, tamper-evident storage, access controls, structured audit-trail retrieval) produces the evidence your compliance team takes to internal or external audit. We don't sit in the trust boundary.

One exception worth naming: if you take the Audit Ledger as a Zyvra-managed service, we hold ongoing operator access, and some procurement teams will reasonably ask for SOC 2 covering Zyvra as that operator. The evidence store itself still holds no PII and runs in your own account; the question there is about the managed-service access, not the data. We'll talk it through honestly on the call.

If your procurement process requires a vendor-level SOC 2 from Zyvra itself, we're not the right fit and an engineering services firm with that certification is. We'll tell you that on the first call rather than waste anyone's time.

Start the conversation

Start with a free scoping call. You leave with one fixed price.

If the pricing makes sense for your situation, the next step is a free 25-minute scoping call. We'll talk through your project shape, confirm which tier you're in, quote the single fixed number, and tell you honestly if we're the wrong fit. Two business day response, NDA on request.

Book a free scoping call