The Nebulae roadmap starts with useful proof-of-concept modules and grows toward controlled imports, approval-based exports, delivery workflows, platform administration, and a future multi-company SaaS architecture.
The first priority is proving practical value with real workflows before overbuilding the SaaS layer.
Continue building Quasar as the core catalog and PIM command center, including base parts, applications, attributes, ACES, PIES, and combined export workflows.
Continue using Aperture to prove value through image coverage, folder gaps, asset quality, metadata checks, 360° depth, and Azure sync analysis.
Expand Orbital from state-level VIO into broader market opportunity views, including national, ZIP, DMA, and Canada-level analysis.
Use Chronicle as the historical intelligence layer for catalog health snapshots, asset coverage trends, Azure sync history, and future platform change tracking.
Continue developing Atlas as the research intelligence workspace for vehicle focus, selected VIO, missing opportunity, and configurable company research modules.
Build the public Nebulae website with module pages, pitch page, FAQ, roadmap, and future demo/contact pages.
The product roadmap focuses on controlled workflows: generate data, validate it, review it, approve it, and then deliver it.
Keep strengthening Quasar’s ACES and PIES export workflows, including combined ZIP exports and consistent data generation.
Add a separate scheduled export run workflow so generated export runs can be reviewed before anything is delivered.
Let users download and review generated files, then approve or cancel the run before future delivery channels are triggered.
Build safe import workflows using templates, validate-only uploads, staging tables, review screens, row-level errors, and approved commits.
Support ACES and PIES flattening, controlled load sheet generation, and internal base part matching for safer Quasar imports.
Delivery should come after the approval workflow is proven. The goal is to prevent automated delivery before users can review and approve generated files.
Create reusable email subjects and body templates for scheduled export delivery workflows.
Define where approved export files should go, who receives them, and which delivery method should be used.
Add delivery options for approved exports after review and approval workflows are in place.
Support future OptiCat API delivery using customer-specific product line and API key configuration.
Nebulae should generate files first, allow users to analyze them, require approval, and only then deliver approved outputs through configured channels.
The SaaS roadmap should be built carefully after the practical workflows prove value.
Add an owner-controlled administration layer above the application for managing companies, master users, module access, and provisioning.
Introduce a platform master database for companies, users, database connection records, module enablement, provisioning jobs, and platform audit logs.
Move toward separate company databases so each tenant’s catalog and operational data can remain isolated.
Support high-level company user groups for platform module access and Quasar/catalog-specific groups for detailed catalog permissions.
Prepare the platform for a future Microsoft/Azure-hosted deployment using Microsoft SQL Server and scalable cloud infrastructure.
The long-term vision is a modular automotive data platform that grows from one company’s workflows into a commercial SaaS product.
Clients should be able to manage catalog data, validate imports, review exports, monitor asset health, analyze market opportunity, track history, and discover research gaps in one connected platform.
Nebulae has a narrow, practical market focus with multiple module expansion paths. Each module can provide value on its own while contributing to a broader platform story.
Nebulae does not need to become everything at once. The strongest path is to prove useful workflows first, then expand into controlled automation, delivery, administration, and SaaS scale.