Parent app layer
Marketing site, shared nav, login flow, dashboard shell, and settings.
DVGProOS core platform
One operating system for every AI business tool we launch.
DVGProOS is the shared foundation for auth, projects, billing, generation, and product modules. Build the platform once, then use saasForge to define LocalLaunch and every future SaaS product.
Core status
Ready for structure buildout
Static shell deployed cleanly for Plesk, Apache, and nginx.
Shared layers
Auth, projects, billing
Factory module
saasForge first
First product
LocalLaunch
Deployment
Subdomain path ready
Shared foundation
DVGProOS is built as reusable layers, not one-off apps.
Registry layer
A single source of truth for product names, routes, versions, and capabilities.
Project layer
One project structure for all SaaS modules so user work stays portable.
Generation layer
Store prompts, outputs, markdown, HTML, and model metadata in one shared shape.
Product registry
Start with DVGProOS core, then saasForge, then LocalLaunch.
| Product | Key | Version | Purpose |
|---|---|---|---|
| DVGProOS | dvgproos |
0.2.0 | Shared platform shell, landing site, and future app core. |
| saasForge | saasforge |
0.1.0 | SaaS creator and product factory. |
| LocalLaunch | local-launch |
0.1.0 | Website copy, landing page structure, SEO sections, and lead forms. |
Plesk deployment
Safe to deploy on Apache and nginx through the subdomain path.
This first shell is static and Plesk-friendly, so it can live in the subdomain document root without disturbing the main WordPress site.
Deployment target
/os.dvgpro.com
Use the subdomain path you created in Plesk and keep additional deployment actions off until we add a build step.
Next build path
Now we can turn this shell into the real product system.
1. Shared app shell
Navigation, product switching, and dashboard framing.
2. Product modules
saasForge specs first, then LocalLaunch generation flow.
3. Persistence
Projects, generations, and export-ready output storage.