Startup & shared services
Bring bootstrap, service setup and application lifecycle into a consistent project foundation.
Foundation
Build your next Unity game on a reusable foundation.
A proposed Foundation Solution for the application systems that sit beneath your game's features.
An idea under exploration. Scope and timing are undecided.
Is it a fit?
A starting point for your project.
For Unity teams that need a consistent starting point for application startup, services, settings and saved data across a project or multiple titles.
Concept — not available
Before you plan around it
Concept. The commercial boundary is unresolved: some foundation features may be a separate Solution, while shared infrastructure belongs within other Solutions.
Planned product scope
What it aims to bring together.
Candidate capabilities, subject to release verification.
Everyday game infrastructure
Coordinate save data, time, settings, input and UI infrastructure.
Project setup & diagnostics
Connect build context, permissions, consent, diagnostics and testing with the setup workflow.
Know the boundaries
Scope & compatibility.
Review the intended installation and the evidence still needed before release.
Solution or shared dependency?
The product boundary must distinguish customer-facing foundation features from infrastructure already required by another Solution. Required shared dependencies are intended to be included with the product that needs them.
Platforms & project fit
Platform, input, consent and build integrations must be selected and verified for the project's Unity version and target platforms. No supported configuration matrix is published yet.
Existing projects & adoption
Adapting an existing project's startup, saves or service lifecycle needs project-specific assessment. No automatic migration path is claimed.
Product evidence
Demonstrations to come.
A settings or project-bootstrap demonstration is proposed. A verified end-to-end sample and release documentation are not published here yet.
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
Foundation software license
A proposed Solution license would include its required shared dependencies. Final product inclusion, support terms and a purchase destination are not published yet. Project implementation is a separate engagement.
Ask about the productSeparately scoped services
Foundation Integration
Discuss the foundation your project needs, its existing architecture and the setup or adaptation work involved. Product boundaries and supported configurations must be established before delivery is scoped.
Discuss foundation integrationCompare 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.
How working together works.
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.
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.
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 Foundation concept? Describe the problem you'd want it to solve. This is an expression of interest, not a preorder or a release commitment.
