Spline-authored streets
Lay out road centerlines with Unity Splines, then generate configurable street surfaces from reusable width, lane and material profiles.

Shape complete streets along Unity splines, then fit them to the terrain.
Bloomways is a proposed standalone Unity authoring tool for laying out connected streets from reusable profiles, lanes and junction pieces.
An idea under exploration. Scope and timing are undecided.
Is it a fit?
For Unity teams building towns, neighborhoods or road networks that need more control than a single road mesh. The concept focuses on editor-time street authoring through Unity's Splines package.
Before you plan around it
Concept. No working package, supported Unity version, performance profile or production compatibility evidence exists yet. The scene illustrates intended workflows, not current software output.
Planned product scope
The initial concept concentrates on the street geometry and terrain relationship requested for a useful first product boundary.
Lay out road centerlines with Unity Splines, then generate configurable street surfaces from reusable width, lane and material profiles.
Compose medians, turn lanes, junctions and intersections while keeping connected approaches and lane transitions coherent.
Build sidewalks and street edges alongside the road, with a planned workflow for conforming grades and surrounding terrain.
Know the boundaries
Review the intended installation and the evidence still needed before release.
The concept is intentionally built around Unity's Splines package. Supported package and editor versions, upgrade behavior and installation requirements must be defined and tested before release.
The first release boundary must define what is editable, what is generated, how junctions are rebuilt and how user-authored overrides survive changes. Runtime road generation is not promised by this concept.
Terrain conformance can affect grading, cut and fill, mesh topology, colliders, navigation, materials and existing scene content. Supported terrain workflows and safe regeneration rules require implementation evidence.
Product evidence
The current evidence is a product concept and visual direction only. A credible demonstration should show a spline edit rebuilding a street, a lane transition, a junction and a terrain-conforming section inside Unity.
Availability & working together
Concept — not available. Scope and timing are undecided. Software licensing and project services are separate offers.
Software · Concept
Bloomways is planned as an independently adoptable asset rather than a required Aether Solution. Package contents, dependencies, Unity versions, price, store destination and release date are not published.
Ask about the productSeparately scoped services
A project-specific street or world-building workflow can be assessed as custom engineering. That work would be scoped separately and does not imply that the Bloomways product is available.
Discuss a custom street systemSoftware licensing and project implementation are separate offers. Product-based setup and integration depend on a verified release and supported configuration; a concept page does not establish availability.
Describe the outcome you need. A short free fit call establishes whether the work is a fit; detailed investigation belongs in discovery.
Where the requirements are uncertain, paid discovery produces findings, risks and a recommended path. Before delivery, we agree on inputs, deliverables, exclusions and acceptance checks.
I deliver against the agreed scope and hand over documentation, test results and known limitations. Ongoing support is a separate agreement.
A direct line to the developer
Interested in the Bloomways concept? Describe the problem you'd want it to solve. This is an expression of interest, not a preorder or a release commitment.