Skip to content
Byte Furnace
Request a Demo
Menu

Smarter Insights. Stronger Games.

From Game Data to Game Intelligence.

Connect your game data, uncover what matters, and turn insights into better decisions with an AI-native intelligence platform built for game studios.

Request a DemoExplore the Platform

Read-only onboarding. Every metric shows its source, time window and freshness.

Illustrative, not customer data.

Your game data is everywhere. Your answers shouldn’t be.

Analytics, revenue, acquisition, game performance and engineering each live in a different tool. Answering one question means exporting, joining and reconciling by hand, and the numbers often disagree.

  • Analytics

    Sessions, retention and funnels

  • Revenue

    Ad and in-app purchase revenue

  • Acquisition

    Campaign and install data

  • Game performance

    Live operations and stability

  • Engineering

    Crashes, builds and releases

One intelligence layer for your game studio.

Each question moves through three stages, and each stage is visibly distinct.

  1. Stage 1 of 3

    Analytics

    What happened?

    Unified, source-attributed metrics across the games and networks you connect.

  2. Stage 2 of 3

    Intelligence

    Why did it happen, and what might happen next?

    An AI Analyst that separates verified metrics from hypotheses and shows the evidence for each finding.

  3. Stage 3 of 3

    Actions

    What should the studio do?

    Recommendations you review. Write actions are off by default and need explicit approval, a dry-run preview and an audit entry.

Analytics Intelligence Actions

Built for the teams that run live games.

  • Unified Game Analytics

    Connected game data in one view, with the source, time window, filters and freshness shown on every metric.

  • AI Analyst

    Ask questions in plain language. Answers label each claim as a verified metric, a finding, a hypothesis or insufficient data.

  • Player Intelligence

    Segment players and see where behaviour changes, with the evidence behind each observation.

  • Monetization Insights

    Follow ad revenue and bidding performance across the networks you connect.

  • Experimentation

    Set up experiments against metrics agreed in advance, then read the results against them.

  • Data Quality & Event Mapping

    Map game events to one shared model and flag gaps before they distort a decision.

Capabilities arrive in phases. Integration status is listed under Integrations.

Connect the data you already use.

Each integration connects on its own, with its own permissions, health checks and revoke control. Onboarding is read-only.

  • AppLovin MAX

    First release · read-only

    Bidding and mediation data. Read-only snapshots, change history and alerts.

  • AdMob

    First release · read-only

    Ad unit and ID tracking. Read-only snapshots and history.

  • Firebase

    Planned

    Read-only access to game analytics data, after the first release.

  • BigQuery

    Planned

    Read-only queries against your warehouse, with per-tenant credentials.

  • Google Analytics 4

    Planned

    Read-only access to the GA4 property you choose.

  • Google Play Console

    Planned

    Read-only store and release data.

  • Crashlytics

    Planned

    Read-only stability data for the games you connect.

  • Performance Monitoring

    Planned

    Read-only performance traces and metrics.

  • GitHub

    Planned

    Repository-level access, granted per repository.

No integration is available yet. Status shows the planned order and access level. Google permissions are requested per service: one Google sign-in never grants access to every Google service.

From connection to informed action in four steps.

  1. Step 1

    Connect your data

    Connect each source on its own, with read-only access.

  2. Step 2

    Map and validate events

    Map game events to one model and check data quality before you rely on it.

  3. Step 3

    Explore intelligence

    Explore the metrics, then ask the AI Analyst for findings with their evidence.

  4. Step 4

    Take informed action

    Review each recommendation. Any write needs explicit approval and is audited.

Designed for trust from the first connection.

  • Tenant isolation

    Each studio works in its own isolated workspace. Access is checked on the server.

  • Least-privilege access

    Each integration requests only the permissions its features need.

  • Read-only onboarding

    Connecting a source never writes to it.

  • Auditable actions

    Every write is logged, after an approval and a dry-run preview.

  • Independent revocation

    Disconnect one integration without touching the others.

These are design commitments for the platform.

Build stronger games with better intelligence.

Request a demo to see how Byte Furnace would work with the data your studio already has.

Request a Demo