Skip to content
Menu

Bloomways

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?

A starting point for your project.

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.

Concept — not available

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

Build the network, not every segment by hand.

The initial concept concentrates on the street geometry and terrain relationship requested for a useful first product boundary.

Spline-authored streets

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

Lanes, medians & junctions

Compose medians, turn lanes, junctions and intersections while keeping connected approaches and lane transitions coherent.

Sidewalks & terrain fit

Build sidewalks and street edges alongside the road, with a planned workflow for conforming grades and surrounding terrain.

Know the boundaries

Scope & compatibility.

Review the intended installation and the evidence still needed before release.

Unity Splines dependency

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.

Authoring boundary & generated data

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 & project integration

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

Demonstrations to come.

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

The product. Help when you need it.

Concept — not available. Scope and timing are undecided. Software licensing and project services are separate offers.

Software · Concept

A future standalone Unity asset

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 product

Separately scoped services

Need a road workflow for your project?

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 system
Compare service options & how we work together

Software 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.

Assisted Setup

Your project fits a supported configuration and you need help getting started.

What you receive

Project preflight, installation, supported provider configuration, a checked reference flow and handoff notes.

Scope & engagement

Custom UI, data migration, unsupported providers and major architecture changes need a separate scope.

Fixed scope once the setup checklist confirms the fit.

Discuss setup

Production Integration

You need a supported product adapted to your existing game and its systems.

What you receive

Discovery, an integration plan, agreed project changes, provider and data integration, testing and handoff.

Scope & engagement

New provider adapters, broad redesigns and unrelated features are scoped separately.

Fixed scope for verified configurations. Uncertain work starts with paid discovery, then agreed milestones or time and materials.

Discuss integration

Custom Engineering

You need custom Unity UI, a new adapter, a migration or behavior beyond an existing product's scope.

What you receive

Agreed project-specific implementation, documentation and tests, with architectural work where needed.

Scope & engagement

The written scope defines what is included. New requirements are agreed before adding work.

Milestones or time and materials, with written change control.

Discuss custom work

How working together works.

  1. Start with a conversation

    Describe the outcome you need. A short free fit call establishes whether the work is a fit; detailed investigation belongs in discovery.

  2. Define the work

    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.

  3. Build, test and hand over

    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

Tell me what you're building.

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.

Inquiry delivery is loading. See the privacy notice for how submissions are handled.

Inquiry details
Use the name you would like us to use when replying.
We use this only to reply to your inquiry.
A short description of your project and the support you need is enough.