Skip to content
For Sellers

How to Set Up a Live Demo for Your Web App

A technical guide to web app live demo setup for code sellers: choosing a demo model, seeding realistic data, one-click role logins, automatic resets, and locking down email, uploads and settings so the demo stays safe and fast.

• Nov 17, 2026 • 10 min read
How to Set Up a Live Demo for Your Web App

A good live demo lets a stranger log in with one click, see the app full of realistic data, try the main workflow, and leave without being able to break anything for the next visitor. To get there you need four things: a demo environment separate from everything else, a seeder that creates believable data, an automatic reset on a schedule, and a short list of features that are disabled or faked in demo mode.

For buyers of source code, the demo is the closest thing to a test drive. It is one of the main trust signals covered in our guide on how to sell your web app or SaaS source code, and on AppTrovo a demo URL is required by the product submission checklist unless your product genuinely has no interface, such as an API-only backend. This article is the technical part: how to build the demo so it works on day 300 as well as on day one.

Examples use Laravel because many products on the marketplace are built with it, but every idea applies to other stacks.

Which demo model should you choose?

There are four common ways to run a public demo. Most sellers should start with the first and only move to the second if visitors keep interfering with each other.

ModelHow it worksStrengthsWeaknesses
Shared demo with scheduled resetOne install; everyone uses the same accounts; data is restored every hour or soCheap, simple, works for almost any appVisitors see each other's changes until the next reset
Per-visitor sandboxEach visitor gets a fresh tenant or database, deleted after a few hoursClean experience, no interferenceMore code and more server resources; needs cleanup jobs
Read-only demoVisitors can browse but writes are blockedNothing can be broken or abusedBuyers cannot try the core workflow, which weakens the demo
Video walkthroughA recorded tour instead of a live installZero maintenanceBuyers cannot explore; best as a supplement, not a replacement

If your product is already multi-tenant, a per-visitor sandbox is often easy: create a new tenant from a template on first visit and delete tenants older than a few hours. For single-company apps, the shared demo with resets is the practical choice.

Step 1: Create a separate demo environment

Never run the demo on the same server, database or storage bucket as anything you care about. A public demo with admin access is an invitation to probe.

  1. Use its own subdomain, such as demo.yourproduct.com, with its own TLS certificate.
  2. Give it its own database user with permissions only on the demo database.
  3. Use a dedicated environment file with a flag such as APP_DEMO=true, so your code can check config('app.demo') in one place.
  4. Turn off debug mode. APP_DEBUG=false on a public demo is mandatory; a stack trace can leak paths and configuration.
  5. Use fake credentials for every third-party service: test-mode payment keys, a log or sandbox mailer, no real SMS gateway.
  6. Deploy the same build buyers download. A demo that runs a newer or older version than the ZIP creates confusion and support tickets.

Step 2: Seed realistic demo data

An empty dashboard sells nothing. The demo should look like a business that has used the app for a few months. Write a dedicated seeder, for example DemoSeeder, separate from the minimal seeder your buyers run on install. The Laravel seeding documentation covers the mechanics.

What makes demo data believable

  • Dates relative to today. Generate records with offsets such as now()->subDays(rand(1, 90)). Hard-coded dates make the demo look abandoned within weeks, and charts show empty months.
  • Plausible names and amounts. Use a library such as Faker with a fixed seed so the data is the same after every reset, then hand-write the records that appear in screenshots.
  • Every status represented. Show paid, overdue and draft invoices; open, pending and closed tickets. Buyers want to see how each state looks.
  • Enough volume to test pagination and search, but not so much that reports become slow. A few hundred records per main table is usually right.
  • Uploaded files and images. Seed avatars, product photos or documents from a folder in the repository, so pages do not show broken images.
  • No real people. Never use exported data from a client project, even "anonymized". Generate it.

A data story helps

Pick a fictional business and seed data that fits it: "Greenleaf Landscaping, 12 staff, 140 customers, jobs scheduled this week." A coherent story makes reports and dashboards meaningful, and it lets you write a short guided tour on the login page ("Open today's schedule and drag a job to another technician").

Step 3: Make logging in effortless

Each extra step between clicking "Live demo" and seeing the app loses visitors. Show the demo accounts directly on the login page in demo mode:

  • One button per role: "Log in as Admin", "Log in as Manager", "Log in as Staff", "Log in as Client". Each button fills the form or posts to a demo-only login route.
  • Credentials shown as text as well, for visitors who prefer to type them, and for your listing's demo section.
  • A frontend or customer-facing link if the app has one, such as a booking page or client portal.
  • A banner on every page: "Demo mode. Data resets every hour. Emails are not sent." This prevents confused bug reports.

Guard the one-click route so it exists only when config('app.demo') is true. Shipping a passwordless login route in the buyer's download, even disabled, is a risk you do not need.

Step 4: Reset the demo automatically

Visitors will delete records, change settings and upload odd files. A scheduled reset puts everything back. Pick the strategy that matches your data size.

Reset strategyHowGood for
Rebuild with migrations and seedersRun php artisan migrate:fresh --seed --seeder=DemoSeeder --forceSmall to medium datasets; always matches the current schema
Restore a database snapshotSeed once, dump the database, then restore the dump on each reset (for example with pg_restore or mysql)Large datasets where seeding takes minutes
Recreate a containerRun the demo from an image with baked-in data and replace the container on scheduleContainerized products; cleanest isolation
Delete per-visitor tenantsA job removes sandboxes older than a set ageMulti-tenant products using per-visitor sandboxes

A reset command that does not break sessions

Wrap the reset in one command, such as demo:reset, and schedule it with the framework scheduler, for example Schedule::command('demo:reset')->hourly(). See the Laravel task scheduling docs. The command should:

  1. Put the app in maintenance mode, with a friendly "Demo is resetting, back in a minute" page.
  2. Rebuild or restore the database.
  3. Clear uploaded files from public storage and copy the seed files back.
  4. Clear caches, queued jobs and sessions, so visitors are not left logged in as users that no longer exist.
  5. Bring the app back up and request the home page once to warm caches.

Hourly works for most apps. If your reset takes more than a minute, run it less often or move to snapshots. Show the time of the next reset in the demo banner if you can.

Step 5: Lock down what visitors must not change

Some actions are harmless in a buyer's install and harmful in a public demo. Block them in demo mode, ideally in one middleware or policy so you can see the full list at a glance.

  • Outgoing email and SMS. Use the log mailer so nothing leaves the server. Otherwise your demo becomes a free spam relay through the "invite user" form.
  • Passwords and emails of demo accounts. If a visitor changes the admin password, every other visitor is locked out until the next reset.
  • Uploads. Restrict file types and sizes more tightly than in production, and never serve uploaded files from a path where they could execute.
  • Outbound requests. Webhooks, "test connection" buttons and URL importers can be abused to make your server call other servers. Disable or fake them.
  • Installer, backups, updates and system settings. Hide screens that reveal paths, environment values or allow running commands.
  • Payments. Use the payment provider's test mode and show the test card number on the checkout page.

When an action is blocked, show a clear message ("Disabled in the demo") instead of a 403 page, so visitors know the feature exists. Add rate limiting on login and form submissions as well; the OWASP Top Ten is a useful reminder of what attackers try first on public web apps.

Step 6: Keep the demo out of search results and monitored

  • Add a noindex rule. You want your listing to rank, not your demo's admin pages with fake data. Google explains the options in its guide to blocking indexing with noindex.
  • Monitor uptime. A free uptime checker that alerts you when the demo is down is worth setting up. A broken demo on a listing loses sales silently.
  • Check the reset log. Log the start, end and result of each reset and alert on failures. A failed reset that leaves the demo in maintenance mode is a common, avoidable outage.
  • Watch disk space. Uploads, logs and old snapshots grow. Rotate logs and clean storage during the reset.
  • Update with every release. Deploy the demo from the same tag you package, and add "Demo updated" to your release checklist. Our guide to support, updates and versioning includes that checklist.

Live demo checklist

  1. Separate subdomain, database user and storage.
  2. APP_DEBUG=false and a demo flag in the environment.
  3. Test-mode keys for all third-party services; log mailer for email.
  4. Dedicated demo seeder with relative dates, every status and seeded files.
  5. One-click login per role, credentials shown as text, demo banner on every page.
  6. Scheduled reset that clears database, files, caches, queues and sessions.
  7. Blocked password changes, outbound requests and dangerous settings screens.
  8. Rate limiting on login and forms.
  9. Noindex on the demo, uptime monitoring and reset alerts.
  10. Demo version matches the downloadable version.

Once the demo is solid, link it from the first screen of your listing (see how to write a product listing that sells code) and add the demo URL in the product form when you list the product on AppTrovo.

Frequently asked questions

How often should a public demo reset?

Hourly is a sensible default for a shared demo. Reset more often if visitors frequently leave the demo in a broken or embarrassing state, and less often if the reset takes long or your data rarely changes. Always show visitors when the next reset will happen.

Should the demo give full admin access?

Yes, in most cases. Buyers want to see the admin panel and settings because that is where they will spend their time. Give full admin access but block the small set of actions that would break the demo for others or expose the server, such as changing demo passwords or running backups.

Do I need a demo if I have a video?

A video helps, but it does not replace a live demo. Buyers use the demo to check speed, layout on their own device and details a video skips. Use the video as a quick overview and the demo as the proof.

How do I stop spam through my demo?

Route all email to a log driver, disable SMS and outbound webhooks, rate limit forms and logins, and reset regularly so any injected content disappears. Never let the demo send real messages to addresses visitors type in.

Can I run the demo on cheap shared hosting?

You can if the host supports cron and your reset finishes quickly, but a small VPS is usually more reliable and lets you isolate the demo properly. Whatever you choose, keep the demo away from servers that hold real data.