INVITE-ONLY BETA NexaPanel 0.2.0-beta.8-rc.29 — installs need a beta invite code. SHA-256-verified artifacts. How to install
Docs

Using the live demo

The public demo is a real NexaPanel 0.2.0-beta.8-rc.29 instance in demo mode: demo.nexapanel.io.

Credentials

The demo login page shows its own credentials — an admin demo account and a customer demo account — so you can see both perspectives. No signup, no email needed.

These are panel logins, not database logins. admin_demo and user_demo sign in to NexaPanel itself. They do not sign in to MariaDB. Database credentials are intentionally not published on the shared demo.

What to try

  • The dashboard, applications, sites, domains, files and logs views
  • Node.js and Laravel application pages, and the Deployment Center
  • Admin views: users, packages, and the Update Center screens

Databases and phpMyAdmin

phpMyAdmin is installed on the demo host, and the demo shows the same phpMyAdmin row action used on real installs: the Databases page links straight into phpMyAdmin, exactly as on your own install. The shared public panel credentials do not log into MariaDB; database credentials are intentionally not published on the shared demo.

On your own install you create a database in NexaPanel, choose its credentials at that moment, and use those to sign in to phpMyAdmin.

How it's kept safe

  • Fake data: everything is seeded sample data on a dedicated host, isolated from any customer or tester server.
  • Resets every 6 hours: the environment is restored to its seeded baseline on a schedule — panel data and the demo databases alike — so changes are temporary by design.
  • Updates are blocked: in demo mode the prepare, activate, apply and rollback actions all refuse and are audited.
  • No real actions: demo mode performs no real provisioning; no real licenses or tokens exist there, and the production licensing service is not connected.
  • No shell: NexaPanel has no web terminal or shell endpoint — in the demo or anywhere else.
Shared environment. Please don't run destructive workloads or upload real personal data. For security testing, coordinate with us first.