Inside the Buildgrain sample workspace
What actually happens when you sign in to the public sample app: seed cloning, owner access, and the nightly reset that keeps the demo honest.
The public sample app at demo.buildgrain.com is not a video and not a click-through mockup. It is the kit itself, running in demo mode with sample data.
Your own workspace, seeded on first sign-in
When you sign in with Google for the first time, the kit clones the sample-co seed template into a private sample workspace and assigns you the owner role. Concurrent visitors never see each other's workspaces — the same tenant isolation rules that ship in the kit apply to the demo.
What the chips mean
Every sample surface carries its boundary chips: Sample data, No customer data, No charge path. They are not decoration. The demo has no charge path at all — the Plan & access simulator switches sample plans and re-syncs entitlements without touching any external provider.
The nightly reset
Three protected seed accounts are restored to their seed state every night. Visitor workspaces are removed 24 hours after their last activity. That is why the demo always looks freshly seeded: it is.
Why this matters
A starter kit is judged by what it does under a real session, not by its screenshots. Open the sample app, create a project, complete a task, switch a sample plan — then open the admin console and watch the same data appear in the cross-account registry.