Skip to content
Vice Drip
Proof Center

We show our work.
Gaps included.

Most FiveM stores overclaim: perf adjectives, resmon numbers nobody measured, “dupe-proof,” fake reviews, invented revenue. Our differentiator is the opposite posture — we publish our proof state honestly, including what has not been proven yet.

This page makes no availability, price, or performance claim. There is no Buy button on it. Every runtime and performance figure reads Pending Shadow bench because no Shadow bench result has been published and no resmon figure has been measured. What is real — and provable by reading the code — is the engineering discipline below.

Runtime proof

0 / 19

public products have a published in-world core-loop capture. No runtime proof published — pending Shadow bench. No live-gameplay screenshots exist; we do not fabricate or borrow stills.

Resmon (idle / active / peak)

Pending Shadow bench

None exists. The studio's idle/active targets are design goals, not readings — labeled [measured-pending] until a real client produces a real figure. No green-graph overlay is shown.

Cleared to sell

0

products. Publishing is gated portfolio-wide. Free tools stay free and open; paid products carry no purchase path until the studio clears them.

The honest ledger

Product status matrix.

One row per public product — its true current status, not its ambition. Every runtime and resmon cell reads pending because none has been measured.

ProductStatusRuntime proofResmonCheckout
ForgeCorevf_coreFree · OpenPending Shadow bench[measured-pending]Free · open
CityPulsevf_announceFree · OpenPending Shadow bench[measured-pending]Free · open
MoneyTrailvf_bankingIn build · proof-pendingPending Shadow bench[measured-pending]Not for sale
ShiftWorksvf_jobsIn build · proof-pendingPending Shadow bench[measured-pending]Not for sale
TitleLock Garagevf_garageIn build · proof-pendingPending Shadow bench[measured-pending]Not for sale
Heatlinevf_drugsIn build · proof-pendingPending Shadow bench[measured-pending]Not for sale
ClosingTablevf_realtyIn developmentPending Shadow bench[measured-pending]Not for sale
CleanTitle Housingvf_housingIn developmentPending Shadow bench[measured-pending]Not for sale
MainStreetvf_businessIn developmentPending Shadow bench[measured-pending]Not for sale
Watchtower Adminvf_adminIn developmentPending Shadow bench[measured-pending]Not for sale
TurfLedgervf_gangsIn developmentPending Shadow bench[measured-pending]Not for sale
CaseLink MDTvf_mdtIn developmentPending Shadow bench[measured-pending]Not for sale
ChainLock Evidencevf_evidenceIn developmentPending Shadow bench[measured-pending]Not for sale
LifeLine EMSvf_emsIn developmentPending Shadow bench[measured-pending]Not for sale
K9 Tracevf_k9In developmentPending Shadow bench[measured-pending]Not for sale
SkyWatch Reconvf_dronesIn developmentPending Shadow bench[measured-pending]Not for sale
SkyForge ShowspyrotechIn developmentPending Shadow bench[measured-pending]Not for sale
Sidekick Litevf_companionIn developmentPending Shadow bench[measured-pending]Not for sale
Veilbreakers: Daemon Protocolvf_daemonIn development · not for salePending Shadow bench[measured-pending]Not for sale

Products on internal hold have no public page, card, price, or waitlist, and do not appear here. “In build · proof-pending” means the code exists and the bench does not — no product has earned an in-test claim.

The engineering moat

Server-authority discipline — provable by reading the code.

This is the section that carries the page. It is not gated on a bench, because it is an architecture fact — described as design and static-model properties, never as runtime-proven. Security is tamper-evident and dupe-resistant, never absolute.

Server-authoritative — no client trust, ever

Every net event validates its source, permission, rate limit, and argument types on the server. The client never holds authority. This is a fact you can read in the code, not a runtime claim.

Sell-once / INVARIANT-R

Money surfaces mutate exactly once — integer payouts, sell-exactly-once paths, owed-record handling — modeled to prevent mint-races and double-sells. Headless money models are GREEN and mutation-tested at the static layer; live-DB replay is still owed.

Append-only audit

State-changing actions leave an append-only receipt — evidence chains, banking audits, realty ledgers. Corrections append a corrective entry; history is never edited. Tamper-evident by construction, never 'tamper-proof.'

Single bridge, no framework lock-in

One free, fully-open ForgeCore bridge spans Qbox, QBCore, and ESX Legacy. You can audit every line of the layer your city would run before anything paid touches it.

When you need help

The install support promise.

01

Intake

You open a ticket with your product, framework, and stage. Secrets are stripped before anything is stored.

02

Triage

The case is graded S1-S4 by severity; anything touching money integrity halts the lane.

03

Evidence

A fix is grounded in your actual error and the docs — never a guess.

04

Escalation

Low confidence, money, licensing, or a repeat failure routes to a human automatically.

05

Resolution

Nothing is called 'fixed' without a fresh debug-level log or resmon read. No warranty or liability language.

Install support covers live products; products in development offer a pre-purchase compatibility check only. Go to Support →

Named first

Known limitations.

  • No runtime proof is published — no product has a published capture of its core loop completing in a live FiveM world.
  • No resmon figure is published — the studio's idle and active targets are design goals, never measurements, and no target is printed here as a result.
  • Publishing is blocked portfolio-wide pending the studio's platform license read.
  • Several products still owe customer doc sets and test harnesses.
  • No gameplay media exists — every image on this site is illustration, key art, or a labeled UI fixture, and none of it was captured from a running server. No trailer has been produced.
  • No product has passed the final release-gate sign-off.
The editorial standard

The no-fake-claims promise.

  • We do not publish performance numbers we have not measured.
  • We do not publish reviews we did not receive, or ratings, testimonials, install counts, or revenue.
  • We do not claim runtime results we cannot show a server log for.
  • We do not claim next-console or future-Rockstar compatibility. Portability is an architecture goal only.
  • When something is unproven, this page says so — a placeholder is a promise of honesty, not a claim.
The path to live

What unlocks launch readiness.

Nothing ships until each of these clears, in order. This is the gate ladder every product walks before a single claim or price goes public.

  1. 01

    Runtime bench pass

    The core loop completes in a live FiveM world on a Shadow-PC bench, with a server log and a screen capture on file.

  2. 02

    Resmon measured

    A real idle / active / peak reading is taken on a real client and filed — replacing the target with a measurement.

  3. 03

    Release-gate sign-off

    The product clears the studio's engineering quality gate.

  4. 04

    Escrow packaging

    A file-level manifest states exactly which files ship open and which ship escrowed.

  5. 05

    License clearance

    The legal and license read clears — a hard blocker for paid and free alike.

  6. 06

    Pricing lock

    Final prices are set; provisional bands are retired.

  7. 07

    Claims sweep

    Every public claim is re-checked against measured reality before anything goes live.

No runtime proof is published across the portfolio; no performance figure is published; nothing is launch-ready; nothing is cleared to sell. Products are FiveM-today (Lua 5.4). When a bench lands, this page changes — date, product, loop completed, server log, and capture — rather than the number quietly changing on you.