Aurora

The problem

Modern organizations increasingly rely on specialized SaaS platforms to support different stages of the customer journey. While operationally efficient, this creates a significant infrastructure challenge: unifying multiple independently hosted applications behind a single domain. Traditional DNS was never designed for path-level traffic orchestration. Without an intelligent routing layer, subpaths can collide, user journeys become fragmented, and valuable SEO authority is diluted across disconnected services. Solving this challenge requires more than domain configuration, as it demands an architecture capable of routing, coordinating, and scaling disparate platforms as a cohesive digital experience.

The approach

To validate the architecture, I built Aurora Yindi, a live luxury boutique proof-of-concept spanning multiple SaaS platforms. The homepage is hosted on ConvertKit, while the sales funnel is served from Carrd, reflecting a common platform fragmentation challenge. Both platforms operate on their free-tier plans, reflecting the budget constraints often faced by startups and small businesses.

Using Cloudflare Workers as an edge-routing layer, I unified these independently hosted applications behind a single domain. Requests are intercepted at the network edge and dynamically routed to the appropriate platform, creating a seamless user experience without exposing underlying platform boundaries.

The implementation includes custom proxy and header management to address cross-platform compatibility while supporting metadata consistency and proper SEO indexing in Google Search Console.

Live Application: aurora.99228811.xyz

Conversion Path: aurora.99228811.xyz/sales

Where it stands

Core infrastructure is live; product features and SEO tooling are actively in progress. This page — and the devlog below — will keep updating as Aurora moves forward.

Stack