Skip to content
Menu

LiveOps

Keep your game's content and schedules moving after release.

A proposed LiveOps Solution for coordinating events, offers and player communication as your game evolves.

An idea under exploration. Scope and timing are undecided.

Is it a fit?

A starting point for your project.

For teams that need to change scheduled content, offers or communication after the game is released.

Concept — not available

Before you plan around it
Later concept. Operational permissions, rollback and provider support require verification before this can be relied on in a live game.

Planned product scope

What it aims to bring together.

Candidate capabilities, subject to release verification.

Events & schedules

Connect LiveOps and event scheduling with changes to content and offers.

Remote configuration & experiments

Bring remote configuration and experimentation into the proposed operations workflow.

Player communication

Coordinate news, mailbox messages and analytics with live activity.

Know the boundaries

Scope & compatibility.

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

Operational safety

Permissions, rollback behavior and operational workflows must be tested together before a supported release. The decorative gate artwork is not evidence of those safeguards.

Providers & project environments

Remote configuration, analytics and backend providers are configuration choices, not blanket compatibility promises. Supported platforms and package versions remain unverified.

Tools & custom operations

A custom operations backend, tooling or migration is separate project work. No hosted control panel or managed operations service is implied by this concept.

Product evidence

Demonstrations to come.

LiveOps Offer Rotation is a candidate demonstration. Verified operating workflows, safeguards and product footage 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

LiveOps 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 product

Separately scoped services

Aether LiveOps Integration

Discuss your content schedules, operations workflow and backend needs. Supported integration and any custom tooling or migration need distinct scope and acceptance tests.

Discuss LiveOps integration
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 LiveOps 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.