What ships in the release ZIP
The full Laravel app, installer, storefront, admin panel, customer dashboard, invoices, legal pages, and update verifier ship together.
Marketplace-ready scriptDocumentation
Current product documentation for the release that ships today.
Use this page to understand the current platform surface, the delivery model, the supported service stack, and the release posture before moving into the full guide or live demo.
Live admin proof
What stays on the control plane
Purchase-code preflight, activation receipts, validation, update manifests, signed download links, and vendor ops stay outside the installed package.
Why the split matters
The installed app stays self-contained while secrets, entitlements, and release delivery remain off the customer server.
Current product features
What the product already covers before any add-ons are layered in.
Margin and pricing control
Set plan pricing, add-ons, billing terms, and protected provider-backed sell floors without editing templates.
Landing theme and content editing
The included public theme, demo links, footer links, legal pages, and homepage copy stay editable from the admin side.
Checkout routing
Hide unsupported gateways by currency and keep sandbox or live credentials separated from the admin UI.
Provisioning workflow
Move from payment into VPS records, DNS, OpenClaw deployment, repair states, and lifecycle emails from one flow.
Customer workspace
Users get deployment, billing, orders, renewals, invoices, and secure OpenClaw launch from one dashboard.
Admin operations
Catalog sync, gateway testing, recovery tools, manual linking, updates, and branding stay in the same operating surface.
Add-on-ready delivery
Core updates, future provider add-ons, and MultiClaw runtimes fit the same release pipeline without redesigning the control plane.
App stack
Laravel commerce and operations surface
- Laravel 12, Blade views, queues, scheduled jobs, and webhook processors for the storefront, installer, admin, and customer panels.
- Subscription billing, PDF invoices, localized pricing helpers, and admin-managed content for the public site, legal pages, and email flows.
- Protected updater, rollback archives, and signed manifest verification built directly into the app runtime.
Storefront and control plane
Cloudflare-backed activation and release delivery
- Next.js storefront on Pages for the product site, documentation, installation, and changelog surface.
- Worker endpoints for preflight, activate, validate, deactivate, and signed update manifest delivery.
- D1 for activations and audit data, R2 for release archives, and Access-protected ops routes for vendor-only operations.
Supported services
The current support matrix is concrete, and the expansion path is already defined.
Infrastructure
- Contabo is the active built-in compute provider in the core release.
- Snapshot, backup, restart, cancel, repair, and provider-linking flows are wired into the same VPS lifecycle.
- Hetzner and OVHcloud are planned for the add-on model rather than hardcoded into the first core package.
Billing and gateways
- Stripe, Razorpay, Paddle, Dodo Payments, and Lemon Squeezy are wired into the billing layer.
- Currency-aware gateway visibility keeps unsupported gateway and currency combinations hidden in checkout.
- Orders, invoices, renewal state, cancellation, pending payments, and review surfaces remain inside the core billing model.
Email and operations
- SMTP plus Amazon SES, Brevo, Mailgun, Postmark, and Resend configuration paths are present in admin.
- Email editing uses structured content fields instead of exposing the full HTML shell for every template.
- Provisioning, payment, cancellation, and ready-state notifications stay part of the operational surface.
Changelog
Release notes that keep the storefront honest about what is live now.
v1.0.0
Current release scope
- Public storefront, customer dashboard, admin panel, browser installer, and updater are part of the core release.
- Contabo provisioning, Cloudflare DNS automation, localized pricing, and multi-gateway billing are included in the current platform.
- Signed activation receipts and remote release manifests keep licensing and updates verifiable without shipping vendor secrets in the ZIP.
Next
Planned packaged expansion
- Hetzner and OVHcloud fit the add-on provider path rather than requiring a new core architecture.
- Future runtime packages such as MultiClaw can reuse the same entitlement and updater model.
- Additional landing themes and official add-ons can ship as ZIP-based marketplace packages on top of the current release flow.
Next step
Move from the product brief into the browser install flow.
The installation page stays intentionally short. The full guide remains linked when you want the complete setup checklist, deployment notes, and post-install tasks.