Blueprint Company Public Testing Status

Public testing is not open right now. Applications open when a public-testing wave or release window starts, not beforehand. Until then, Blueprint Company remains a private-testing Roblox building sandbox: talented builders and bug reporters get in through Discord, sign rules, and help Riley stress-test tools before a wider audience arrives.

This page explains the difference between private and public testing, the wave model (everyone accepted across waves, with light device and anti-troll checks), and the only safe way to get a seat. Pair it with How to Become a Tester for the checklist form of the same advice.

Status snapshot (November 2026)

• Full public release: not yet
• Private testing: active (18+, NDA, Discord /apply)
• Public testing applications: closed until a wave/release opens — do not expect a standing open form today
• Wave model: when public testing starts, applicants are accepted in waves; the goal is broad access over time, not a tiny forever-private club
• Light checks: expect device readiness and anti-troll screening rather than a heavy private-style NDA for public waves
• Public Roblox place: not listed yet — ignore random place links that demand payment
• Platform focus: PC first; mobile after PC features mature

Official reminders also live on the Rillcore Studios group and Carrd (https://rillcore.carrd.co/): Blueprint is unreleased, and anyone selling access is running a scam.

Private testing vs public testing

Private testing (current)

Private testing is selective quality control. Riley looks for builders who will showcase the game’s potential, file detailed bug reports, and communicate clearly. Expect:

• Age gate (18+)
• NDA — do not leak private builds, tools, or unreleased UI without permission
• Higher expectations for feedback quality
• Possible furniture modeling or content-creator application tracks alongside playtest seats

Public testing (upcoming — apps not open yet)

Public testing is designed to be broader. Community messaging is clear:

• Applications open on release / when the wave starts, not now
• People are accepted in waves so servers and moderation can scale
• Gates stay comparatively light: confirm you can run the client on a supported device and pass basic anti-troll checks
• Exact forms, age rules, and channel names can change the week a wave opens — always re-read Discord pins (https://discord.gg/U8f3Tynr99)

If someone claims public apps are secretly open while Discord announcements say otherwise, treat that claim as misinformation or a scam funnel.

How to prepare before a wave

1. Join Discord via the Links hub (invite: https://discord.gg/U8f3Tynr99).
2. Verify and find application instructions (/apply or staff guidance) — for private seats now; for public seats only when staff say the wave is live.
3. Confirm you can test on PC during early waves.
4. Draft a short builder bio: styles you build, bugs you are good at spotting, hours you can play.
5. Read Getting Started and Plot System so day-one time goes into building, not confusion.

What public testing is for

Public waves exist to find datastore edge cases, multiplayer permission bugs, performance problems on large 1024×1024 plots, and UX friction in the hub. They are not a finished “launch party.” Expect resets, tool renames, and temporary limits. Keep a personal changelog of bugs you file.

If you want creative practice while waiting, study Building Basics, Roofs, Floors & Pools, Scaling & Transform, Landscaping, Furniture & Decals, and the build tools tier list. Those pages stay useful whether you enter next week or next month.

Scam and safety rules

• Never pay Robux, PayPal, or crypto for “early access.”
• Never download random executors claiming they unlock Blueprint.
• Only trust invites from official Carrd / Discord / group links on Links.
• If a stranger DMs a place file or “private server key,” walk away and report it.
• If someone says public apps are open right now while this page and Discord still say waiting for a wave, walk away.

Blueprint’s entire brand is free building. Paid access contradicts the project. Treat that contradiction as an automatic red flag.

After you get accepted

• Create a small practice plot before a mega-city.
• Set visibility and build permissions deliberately (Plot System).
• Learn controls on PC (Controls).
• Report bugs with repro steps; screenshots help.
• Watch the Feature Roadmap so you know which tools are intentional vs temporary.

Related reading

Continue with How to Become a Tester, Feature Roadmap, Updates Hub, and Community Creators. For philosophy contrasts, see Blueprint vs Bloxburg.

Public testing will not feel like a polished storefront launch. It will feel like a shared construction site that opens in waves. Show up when staff open apps, ready to build, ready to report, and ready to ignore scammers.