Operator reality
What Aurora Solar already handles well
Proof summary
Strongest next step
Solar Installation is the clearest first click from this parent hub.
Live page inventory
1 active Aurora Solar page across 1 approved wave.
Operator pressure
We struggle with getting our custom CRM to correctly map complex utility consumption profiles into Aurora via the API.
Buyer comparison set
OpenSolar, HelioScope, Solo, Sighten
Website gap
Where the website gap starts before Aurora Solar
While Aurora is unmatched for PV design and proposals, it is not a general-purpose marketing CMS or full-scale CRM. Installers still need a dedicated website to drive traffic, nurture top-of-funnel leads, and manage broader marketing campaigns before a specific solar design is initiated.
- Does not provide a full website builder or CMS for SEO-driven marketing.
- Native lead capture widgets (Lead Capture AI) are powerful but offer limited visual customization to perfectly match custom brand guidelines.
- Requires an external CRM for long-term lead nurturing and automated drip sequences.
Fit guidance
Who usually fits an Aurora Solar-centered website rebuild
Recommended fit
- Teams already running Aurora Solar as the system of record
- Operators who need stronger qualification before data reaches Aurora Solar
- Businesses that need a public site and intake flow shaped around construction demand
Caution fits
- Teams expecting undocumented writes or shortcuts inside Aurora Solar
- Organizations that have not decided whether Aurora Solar is the long-term operating system
Not ideal for
- Buyers who only want a visual redesign with no intake or handoff changes
- Teams that need the website to promise workflows Aurora Solar does not publicly document
Traditional agency build
Why this Aurora Solar hub cannot read like a generic agency page
- Generic copy treats Aurora Solar like a logo instead of an operating constraint.
- The website handoff stays vague, so teams keep repairing missing context manually.
- Each new landing page reopens scope because the integration story was never made explicit.
Peak Leverage system
What a real Aurora Solar hub does instead
- Route copy stays aligned with the documented Aurora Solar handoff.
- Public-site language matches the operator pressure the team feels inside Aurora Solar.
- Technical trust, route selection, and next actions stay on one parent hub.
Page explorer
Choose the industry route that matches how Aurora Solar is used
Documentation status
What Aurora Solar publicly documents for native and API handoff
Embed surface
Aurora Solar publicly documents Lead Capture AI website widgets and estimator settings, including a floating discovery bar and lead-to-project handoff behavior.
API surface
Aurora Solar publishes a documented REST V2 at version v2.
Webhook surface
Webhooks can notify your external systems when a design finishes processing or when a customer signs a proposal. This allows you to automatically update CRM deals or trigger automated follow-up emails without polling the API.
Rate limits
API calls are rate-limited per tenant. Heavy batch operations should be queued to avoid 429 Too Many Requests errors, particularly when pulling down heavy design data, 3D models, or PDF proposals.
Versioning
Aurora's Sync API (v2) is the current standard. Ensure endpoints use the /v2/ path, as older v1 endpoints are deprecated and lack newer functionality.
Sandbox
Aurora provides a dedicated Sandbox environment. Customers can generate separate Sandbox API keys to test integrations without affecting production data or incurring design request charges.
Technical trust path
Data primarily flows from the website to Aurora by POSTing a new Project via the Sync API. Often, a CRM acts as the middleman, taking the website lead and pushing the address payload to Aurora to provision the design environment.
Authorization uses Bearer tokens passed in the HTTP request header. You generate and manage these API tokens directly within your Aurora tenant settings, with separate keys available for Sandbox and Production environments.
Check the API and event model
Review API-token auth, the rest api, event delivery, rate limits, versioning, and test-environment realities before you promise a live Aurora Solar sync on the site.
Next step
See whether Aurora Solar is the right handoff layer for your website
We will show the public-facing flow, the intake logic, and the documented Aurora Solar handoff before recommending a rebuild.
The first pass shows where the website is dropping context before Aurora Solar can do its job.