Questions about Nebulae

Nebulae is the overall platform. The individual tools inside it are modules, such as Quasar, Aperture, Orbital, Chronicle, and Atlas. Each module solves a specific automotive data workflow, but they are designed to support a larger connected system.

Nebulae is built for automotive catalog teams, product data teams, digital asset teams, sales and strategy teams, research teams, and companies that work with automotive fitment, ACES, PIES, VIO, product content, and digital assets.

Automotive data work is often spread across spreadsheets, legacy systems, manual exports, file folders, disconnected research tools, and separate asset processes. Nebulae helps organize these workflows into a more controlled and visible platform.

The primary focus is automotive catalog and data operations. However, Nebulae is being designed as a modular platform, so it can grow into related workflows such as digital asset readiness, VIO analysis, research discovery, export approval, import staging, and platform administration.

Quasar is the catalog and PIM command center inside Nebulae. It focuses on base parts, applications, attributes, ACES exports, PIES exports, combined export workflows, and future import/load sheet workflows.

Aperture is the catalog and digital asset health command center. It helps teams monitor image coverage, folder gaps, metadata quality, colorspace readiness, 360° asset depth, Azure sync gaps, and catalog health trends.

Orbital is the vehicle intelligence and market opportunity module. It currently focuses on VIO analysis by state and is planned to expand toward ZIP, DMA, national, and Canada-level views.

Chronicle is the historical intelligence and change tracking layer. It is designed to track snapshots, trends, catalog health history, asset depth history, Azure sync history, and future platform-wide audit/change history.

Atlas is the research intelligence and opportunity discovery workspace. It helps teams define vehicle focus areas, analyze selected VIO, identify missing opportunity, and support configurable company research modules.

That is the long-term direction. Nebulae is being planned as a modular platform, so future companies could potentially enable only the modules that are relevant to their workflows.

Quasar is being built to support ACES export workflows. The current direction includes ACES 4.2 export support and future staged import workflows for ACES-based application data.

Quasar is also being built around PIES export workflows. PIES support is part of the catalog export story, alongside ACES and combined export packages.

Yes, import support is part of the roadmap. The planned approach is controlled and staged: flatten source files, create a load sheet or import template, validate the data, review staged results, and only then commit approved changes.

Yes. Quasar is planned around export workflows such as ACES, PIES, combined ZIP exports, scheduled export runs, approval steps, and future delivery channels.

Yes. Aperture focuses on digital asset and catalog health checks, including image gaps, folder gaps, metadata issues, colorspace readiness, 360° depth, and Azure blob sync issues.

Not necessarily. Nebulae can be positioned as a workflow and intelligence layer around automotive data operations. It may work alongside existing systems, especially early on, while replacing manual spreadsheet-heavy processes over time.

Nebulae is currently being built carefully as a proof of concept and early platform foundation. The long-term goal is to evolve it into a multi-user, multi-company SaaS platform.

That is the planned direction. The future SaaS architecture is expected to support multiple companies, company-specific users, module access, and separate tenant data.

The long-term plan is for each company or tenant to have separated data, ideally with separate tenant databases and a platform owner/admin layer managing companies, users, permissions, and provisioning.

Yes. The roadmap includes platform-level administration, company management, user management, module access, high-level user groups, and Quasar/catalog-specific user permissions.

The long-term plan is cloud hosting, likely using Microsoft/Azure infrastructure and Microsoft SQL Server. The current focus is to build the platform carefully one step at a time before moving into full SaaS infrastructure.

A catalog team would use Nebulae to reduce manual work, improve export/import control, identify catalog and asset gaps, analyze market opportunity, and make automotive data workflows easier to manage.

Nebulae has a focused market, a modular product story, a practical proof-of-concept path, and a long-term SaaS roadmap. Each module can provide standalone value while supporting a larger platform.

Spreadsheets are useful, but they are not ideal for controlled workflows, permissions, validation, history, repeatable exports, staged imports, asset diagnostics, or platform-wide reporting. Nebulae is designed to turn repeatable data work into structured workflows.

The long-term vision is a modular automotive data SaaS platform where companies can manage catalog data, monitor asset readiness, analyze vehicle opportunity, track historical change, discover research gaps, and control user/module access from a scalable platform layer.

The best wording is that Nebulae is in active development and proof-of-concept stage. The current goal is to prove the workflows, polish the platform, and build toward a commercial SaaS version carefully.