Commission-only VR security work

Protection built for your game — not sold off a shelf.

We build anti-tamper and integrity systems for VR multiplayer titles: client hardening, an attestation backend, encrypted telemetry and the detection pipeline behind it. Scoped to your build, quoted before a line is written.

Fixed-price quotes Reply in 24–72h NDA on request
attestation / session join LIVE
01challenge issuedServer sends a one-time nonceSENT
02build signatureRelease manifest matches the signed hashVALID
03runtime integrityNo hooks or patched code sectionsCLEAN
04injected moduleUnsigned library loaded into the processFLAGGED
05verdictDecided server-side, never on the clientREFUSED
Decision: server-authoritative Evidence: written to your dashboard

No subscription

One commission, one fixed price. Nothing recurring unless you ask for a retainer.

You keep the source

Everything we write is handed over with docs. No black box you can't maintain.

Built per title

We work against your build and your threat model, not a generic SDK.

Quote before work

Scoping costs nothing. You see the price and the plan before anything starts.

Services

Pick what you need. We'll quote it.

Tap any service to add it to your brief — the button at the bottom writes the email for you. Take one piece or the whole stack.

Nothing selected yet. Tap the services you want and we'll draft the email. Email this brief
Process

How a commission runs

Five steps, in this order, every time. You know the price before step three.

01

You send a brief

Your game, engine, platforms, player count and what's going wrong right now. A few paragraphs is plenty.

02

Scope and quote

We come back with the service codes we'd use, a timeline and a fixed price. Nothing to pay to get this far.

03

We build

Work happens against a test build you provide. You get progress notes through the job, not silence until delivery.

04

Integration and handoff

We wire it into your build alongside your team, hand over source and documentation, and walk them through it.

05

Support window

Fixes and tuning are included for an agreed period after ship. A retainer is optional after that, never assumed.

Handoff

What you actually get

A commission ends with things you own and can maintain without us.

Source, not binaries

Readable code in your repo, commented, with the build steps that produce it.

Written documentation

How each piece works, what it assumes, and how to change it when your game changes.

Threat notes

What we hardened, what we deliberately left, and where the next attack is likely to come from.

A support window

An agreed period after ship where fixes and tuning are already paid for.

Scope

What we take on

Worth reading before you write to us — it saves a round trip.

We take

  • Games you own or are authorised to work on
  • VR multiplayer titles on any engine
  • Studios, solo devs and community-run servers
  • Small audits before you commit to a full build
  • Emergency work when you're mid-outbreak

We don't

  • Cheats, mod menus, injectors or exploit development
  • Work on games you don't own or have no permission to touch
  • Anything aimed at breaking someone else's protection
  • Collecting player data beyond what detection needs
  • Jobs where you can't tell us what the game is
Questions

Before you write

How much does it cost?
It depends entirely on the game and the scope, so we don't publish numbers we'd have to walk back. Send a brief and you'll get a fixed price for the work described. Scoping itself is free.
Is there a plugin I can just drop in?
No, and that's the point. Off-the-shelf protection gets broken once and then it's broken for everyone using it. We build against your engine, your netcode and the specific abuse you're seeing.
Do I need all of it?
Almost nobody does. Most first commissions are one or two service codes — often an audit, then whichever piece the audit says is actually costing you players.
What do you need access to?
A test build, and enough of your netcode or server setup to integrate against. We don't need production keys or your player database, and we'll sign an NDA before anything is shared.
How long does it take?
An audit is usually days. A single service line is usually weeks. A full stack across several codes takes longer, and the timeline is written into the quote before you agree to anything.
What happens when it gets broken later?
Everything gets probed eventually — anyone promising otherwise is selling something. That's why you get the source and the docs, why there's a support window after ship, and why a retainer exists if you want us on call for the next round.
Contact

Start a commission

No signup, no dashboard, no card form. One address, and a person on the other end of it.

flow.dev@frowlz.dev
Open email

Put this in the first email

  1. Game name, engine and target platforms
  2. Rough player count, and whether it's already live
  3. What's being abused right now, in plain terms
  4. Any protection you already have in place
  5. Service codes you think you want — or ask and we'll suggest
  6. Your deadline, if there is one