The WebGL Sandbox: Load the Demo Engine
The iframe below runs the original Push Gaming HTML5 client on a virtual balance. Same PRNG. Same grid. Zero financial risk.
The sandbox mirrors the live math. But a persistent myth says otherwise. Here is the proof.
Engine Parity: Is the Free Play Math Rigged?
| Parameter | Demo Sandbox | Real Money Mode |
|---|---|---|
| Math Model | Certified PRNG ✓ | Certified PRNG ✓ |
| Hit Frequency | ~27.8% (unofficial avg.) | ~27.8% (unofficial avg.) |
| Server Architecture | Simulated sandbox (virtual credits) | Live CAD transactions |
| Regulatory Audit | Yes — regulators mandate identical logic ✓ | Yes — AGCO-registered operators ✓ |
Regulatory standards require that free-play versions use the same random number generator and return-to-player percentage as real-money versions. The demo is not tuned to pay more — or less.
Identical math means identical grind. The demo will punish you with the same dead spin sequences you will face on a real balance. Use that to your advantage — run a structured test before you deposit.
The 3-Step Stress Test: How to Evaluate Variance
The demo sandbox exists for data collection, not entertainment. Run this protocol before you transition to real CAD. Track numbers, not feelings.
- Base Game Grind Tracking — Run 100 auto-spins on your intended stake level. Count consecutive dead sequences. If the engine delivers 30+ dead spins in a row, that is normal extreme variance — not a malfunction. Record the longest streak.
- Nudge Mechanics Observation — Track how often Seaweed Stacks drop without revealing Golden Sharks. This is the feature tease. Log the ratio of standard symbol reveals vs. Golden Shark activations across 50 Nudge cycles to gauge Razor Reveal frequency.
- Bankroll Bleed Simulation — Set your virtual balance to match your real-world session budget (e.g., C$50). Observe how many spins it survives without a significant feature hit. If it depletes in under 100 spins, your stake is too high for this volatility index. Adjust before going live.
Three tests. Hard data. No guesswork. When the numbers confirm your bankroll can survive the variance — the live engine is one click away.
Transitioning from Virtual Sandbox to Real CAD
The sandbox forgives every mistake. A real balance does not. If your stress test showed bankroll depletion in under 100 spins, lower your stake or increase your deposit — do not chase the same variance on a thinner margin.
Before you switch: set responsible gambling limits in your operator account. Configure session time caps. Confirm the active RTP payload in the in-game paytable — operators can run nerfed versions. Deploy a real bankroll strategy → built on the data you collected here.
Switch to Real Money Engine (C$0.10 Min Stake)One final layer of due diligence: verify the algorithm's integrity before you wager real CAD. Analyse algorithm safety →
Canadian Free Play FAQ: Age Checks & Virtual Credits
Is the Razor Shark demo rigged to pay out more than real mode?
No. Regulatory standards require free-play versions to use the exact same PRNG engine and hit frequency as real-money mode. The demo is an algorithmic replica — not a marketing tool designed to inflate your expectations. Expect the same dead spin protocol and the same extreme variance.
Why do I need to verify my age to play for free without deposit?
Provincial regulations prohibit anonymous access to gambling simulations. The legal gambling age varies by province — 19+ in Ontario, BC, and most provinces; 18+ in Alberta, Manitoba, and Quebec. Age verification protects minors. At AGCO-registered operators in Ontario, identity verification is mandatory even for zero-risk sandboxes.
Can I win real money in the Razor Shark demo?
No. The sandbox uses virtual credits with zero financial value. No withdrawal is possible. The demo exists for variance testing and bankroll calibration. To wager real CAD, switch to the live engine →.
How do I reset my virtual balance in the demo?
Refresh your browser session. The HTML5 client reloads the default simulated bankroll automatically. No account action required. Cross-device: clearing the browser cache on iOS or Android achieves the same result.