Landing pages, hosting package presentation, signup entry points, and trust-building content for Julbie as a real service business.
Julbie Platform MVP
Fresh hosting that feels simple, bright, and under control.
Julbie starts with a hosting-first platform: clear package selection, customer signup, secure payment flow, and automated provisioning inside one polished customer experience. The platform owns the workflow instead of pushing customers into fragmented tools.
Immediate Build Goal
Turn this fresh Laravel project into a usable MVP shell.The next code steps are routing, layout, database model design, authentication, package catalog, checkout orchestration, and asynchronous provisioning flow.
MVP Boundary
Build the hosting engine first.
Account registration, login, dashboard, invoices, and hosting service details under one Julbie-owned customer identity.
Orders, payment confirmation, provisioning jobs, retries, audit history, and Hestia integration handled as application workflows instead of manual admin work.
Execution Order
First build sequence
- Create the base app shell, layout, and Julbie branding.
- Define core models for customers, orders, invoices, packages, and hosting services.
- Add authentication and a customer dashboard.
- Build hosting package catalog and checkout initiation.
- Accept Yoco webhooks and mark orders as paid only after verification.
- Run background provisioning jobs against HestiaCP and record service credentials.
What comes after that
- Supplier-driven product imports come after hosting automation is stable.
- Storage services stay behind the same Julbie portal later, but not in phase one.
- Shared billing, ticketing, and automation patterns should be designed for reuse.
- The long-term cross-business AI layer belongs above the platform, not inside one page.