Everreality installer
Hybrid setup preflight
Proves whether this host can run the control panel, and makes the Docker/runtime boundary explicit for n8n, publishing, AI workers, queues, and future app runtimes.
Checks
0
Works
0
Partial
0
Broken
0
Setup wizard map
Buyer installation progress
This is the durable CodeCanyon setup map: control-plane checks, payment and AI credentials, queue/cron, runtime nodes, and browser proof are tracked separately so no untested slice is called complete.
0%
Read-only setup proof. Browser validation still controls final WORKS status.
Works
0
Partial
0
Untested
0
Broken
0
How this percentage is calculated
WORKS means browser or runtime proof is complete and counts as one full step.
PARTIAL means configured, saved, or technically present, but still waiting for real buyer-flow proof. It counts as 45% of one step.
UNTESTED means no browser evidence yet and counts as zero. So 0% is not a random score; it is the current proof score.
Next proof actions
All installer checklist steps are WORKS. Keep final screenshots in the launch report.
Role proof
Create browser-test workspaces for every buyer role
This explicit installer action creates a proof reseller and proof customer under the platform so a buyer can validate admin, reseller, and customer dashboards without terminal work or hidden seed scripts.
Safety rule
Proof passwords are shown once and reset only while the installer is open. Remove or rename proof tenants before selling a live tenant if demo data is not desired.
Admin
/admin
Platform oversight, setup state, and system checks.
Reseller
/reseller
Tenant commerce, billing studio, servers, customers.
Customer
/dashboard
Workspace billing, plans, websites, deployments.
First owner
Create the platform admin from the installer
This replaces the old terminal-only first-admin step. Existing production installs lock this action unless installer maintenance is explicitly enabled.
Buyer-safe rule
Passwords are submitted once and never echoed back. After this step, the buyer logs in normally and completes runtime, billing, AI, queue, and browser-validation checks.
Hosted setup prefill
Checking whether hosted setup provided owner details.
Configuration
Save bootstrap credentials and service settings
This writes buyer setup values to the package environment and encrypted platform integration settings. Secrets are accepted once, then only masked status is returned.
Lock rule
Configuration writes are available only while the installer is open. After launch, use Admin > System for integrations and controlled maintenance for installer repair.
Step 1 of 6
Razorpay payments
Required before packages, wallet recharge, invoices, and deployment entitlement purchases can work.
Save behavior
This button saves only this step. Razorpay save will not overwrite database, mail, storage, or AI settings.
Mode
test
Key id
Not saved yet
Key secret
Not saved yet
Webhook secret
Not saved yet
Webhook URL for this install: http://localhost:8013/api/webhooks/razorpay
Saved credentials move this step to PARTIAL. It becomes WORKS only after a browser-proven Razorpay test payment and webhook reconciliation.
To make Payments WORKS
Prove checkout and webhook reconciliation
Credentials only prove the keys were saved. WORKS means the buyer can actually purchase a package, Razorpay sends the webhook, and this app reconciles the invoice/payment records.
Create Razorpay webhook
http://localhost:8013/api/webhooks/razorpay
Buy a test package
Use Plans with Razorpay test checkout.
Confirm invoice paid
Billing should show payment and paid invoice.
Refresh installer proof
This step becomes WORKS after records reconcile.
Latest proof refresh
Not checked in this browser session yet
Refresh the proof score after saving credentials or completing a checkout.
After saving, this installer refreshes the readiness checklist. A step remains PARTIAL until its real browser flow is proven.
Install modes
Choose the truthful deployment model
Normal cPanel can host only the control plane unless the host provides real Docker/server access. Runtime workloads must move to connected server nodes.
Environment proof
Preflight checklist
Next required proof
Setup is not complete from this page
This preflight is the first installer slice. Final CodeCanyon readiness still needs credential setup, first admin creation, migrations, seed choice, queue/cron supervision, node heartbeat, and browser validation for admin, reseller, customer, public invoice, storefront, Studio, billing, and deployments.
1. Fix failed critical checks.
2. Create the platform owner in the First owner section, then prove login from the browser.
3. Register runtime servers from Admin > Deployments > Nodes or Reseller > Servers when the package allows it.
4. Prove queue, cron, billing, AI, publishing, and deployment flows through browser evidence before marking them WORKS.