Accounts & sessions
Connect authentication with the player's session and identity.
Player Cloud
Keep player identity and saved progress connected.
A proposed Player Cloud Solution for accounts, profiles and cross-device saves in Unity games.
An idea under exploration. Scope and timing are undecided.
Is it a fit?
A starting point for your project.
For games that need player accounts and saved progress to remain consistent across sessions or devices.
Concept — not available
Before you plan around it
Concept. Provider readiness, save conflicts, account recovery and migration behavior all require verification.
Planned product scope
What it aims to bring together.
Candidate capabilities, subject to release verification.
Player profiles
Bring player-profile data into a shared backend workflow.
Cloud saves
Coordinate cloud saves and backend abstractions for continuity across devices.
Know the boundaries
Scope & compatibility.
Review the intended installation and the evidence still needed before release.
Provider choices
Unity Gaming Services, PlayFab and a custom backend are candidate paths in the product plan. Their inclusion here is not a supported-configuration claim.
Conflicts, recovery & migration
Save conflicts, account recovery and migration must be demonstrated for the chosen configuration. No automatic conflict resolution or account-linking behavior is promised.
Data & project boundaries
Player data models, access ownership and migration needs must be established for the project. Custom identity providers and backend migrations are separately scoped work.
Product evidence
Demonstrations to come.
Authentication Session Flow and Cloud Save Backup Flow are candidate demonstrations. Verified recovery, conflict and migration evidence is 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
Player Cloud 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
Aether Player Cloud Integration
Discuss your account and save flows, selected backend and existing player data. Account linking, migrations or a custom identity provider require specific project scope.
Discuss Player Cloud 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 Player Cloud concept? Describe the problem you'd want it to solve. This is an expression of interest, not a preorder or a release commitment.
