Early access · looking for design-partner studios

Hotfix your Unity game without waiting for a store update.

Remendo patches only the C# methods you changed in an IL2CPP build. Everything else keeps running as the native code you shipped. Patches are signed with your key and checked on every device.

# fix the bug in C#, build the patch, then:
$ remendo patch upload Builds/Patch-v2
✓ signature ok · 3 assemblies · build 7f3c…
$ remendo release create --patch pat_k2m… --percent 5
✓ rel_x3q… live for 5% of installs
$ remendo release set rel_x3q… --percent 100
# looks wrong? roll back in one command:
$ remendo release set rel_x3q… --halt

How it works

You keep writing normal C#. Remendo compares your patched code with the build you shipped and sends only what changed.

Ship a base build

Build your IL2CPP player through Remendo. It records a snapshot of the shipped code and pins your public signing key into the player.

Build a signed patch

Fix the code and build a patch against that snapshot. Changed methods run in Remendo's interpreter; unchanged methods stay AOT-compiled. The patch is signed with a key that never leaves your machine or CI.

Roll out, watch, roll back

Release to a percentage of installs, per build and channel. Raise it when the numbers look right, or halt it and every install returns to the shipped code at its next launch.

Built for live games run by small teams

Designed for studios that run live-ops on mobile and cannot wait days for a review to fix a crash or an economy bug.

Method-level patches

Only changed methods are interpreted. The rest of your game keeps its native AOT code, so you do not pay an interpreter cost for code you did not touch.

Plain C#, no second language

No Lua or scripting layer to maintain beside your game. Your existing C# is what gets patched.

Your keys, your trust

RSA-signed patches, verified on the device against keys pinned in your build. Neither we nor anyone with access to the server can push code you did not sign.

Staged rollouts

Release to 1%, 5%, 50% of installs per build and channel. Raising the percentage only adds installs; nobody flips back and forth.

Instant rollback

Halt a release and installs fall back to the previous release or the shipped code. On the device, a patch that keeps failing to start is switched off automatically.

Hosted or self-hosted

Use Remendo Cloud, or run the same server yourself next to your game backend. Patch files are content-addressed, so any CDN can cache them.

Safety is the product

A hotfix system is code that runs on every player's device. These guarantees hold even if our servers were compromised.

Read the security model →

  • Signed or refused. Unsigned patches, unknown keys, other builds and modified files are refused before anything is loaded.
  • Never mid-session. Downloads are verified, staged and activated at the next launch, never inside a running game.
  • Self-healing devices. A patch that was loaded twice without the game reaching a healthy state is disabled on that device.
  • Minimal data. A random install id, never stored on the server, and aggregate counters per release. No device identifiers.

For fixes, not for bypassing review

App stores allow downloaded interpreted code only within limits. Remendo is built for the use that fits them: fixing and tuning the game players already installed.

Your responsibility as the publisher. Apple's App Review Guidelines (2.5.2) and developer agreement, and Google Play's Device and Network Abuse policy, restrict code that changes an app's purpose or adds unreviewed features. Use Remendo to fix bugs and adjust existing behaviour, keep patches consistent with the app you submitted, and check the current policies of every store you ship to. Remendo does not provide legal advice or guarantee store approval.

Where we are today

We would rather tell you exactly what works than surprise you in production.

AreaStatusNotes
Windows (x64), IL2CPPSupportedOne pinned editor version: Unity 2022.3.62f3. Verified on a native player: base build, signed patch applied without rebuilding the player, tampered patch refused with fallback to the shipped code.
Android, IL2CPP (ARM64)SupportedSame pinned editor version. Verified on Android 12 (emulator, ARM64): base APK, signed patch applied without reinstalling, tampered patch refused with fallback to the shipped code.
iOS, IL2CPPSupportedSame pinned editor version. Player builds need a macOS host with Xcode, as for any Unity iOS game.
Unity versionsIn progressUnity 2022.3 LTS (all patch releases) through Unity 6 and later. Each version moves to Supported once it passes the same native player checks; until then, builds need Unity 2022.3.62f3.
Remendo CloudEarly accessPatch upload, signature checks, staged rollout, rollback, adoption counters. Self-hostable.
Consoles, WebGLNot plannedPlatform rules do not allow downloaded code.

Pricing

Per game, per year, paid by card or PayPal. No per-install fees. Patches you released keep reaching your players even if a license lapses.

Indie

990 USD / year
  • 1 game
  • Remendo package and Remendo Cloud
  • Email support
Buy Indie

Enterprise

Custom
  • More games, self-hosting help, invoicing
  • Bank transfer on request
Contact us

Before you buy: today Remendo supports Windows (x64), Android (ARM64) and iOS IL2CPP players built with Unity 2022.3.62f3. See current status and the terms, including the refund window.

Become a design partner

We are working with a small number of studios with live mobile games on Unity. Design partners get early access free of charge, direct engineering support for the integration, and founding pricing when plans launch.

  • Integration with us, not alone. We help wire Remendo into your build and CI.
  • You set the priorities. Platforms and Unity versions follow what partners ship.
  • Asian time zones covered. Support during your working hours across East and Southeast Asia.
Platforms you ship on

Questions

How is this different from Lua or JavaScript hotfix frameworks?

Those run your hotfix logic in a second language. With Remendo you patch the C# you already have, and only the methods you changed leave AOT code.

What can a patch change?

Code in the assemblies you mark as patchable, which covers most bug fixes and balancing changes. Some changes, such as altering the layout of types already compiled into the player, need a new store build. During early access we review the limits with each design partner against their own code.

What happens if a patch crashes the game?

Halt the release and installs return to the shipped code at their next launch. Independently of the server, a device that launched twice with a patch without reaching a healthy state disables that patch by itself.

How do I pay?

Checkout takes PayPal or a debit or credit card, charged in US dollars by PayPal. You do not need a PayPal account to pay by card, and we never see your card details. Where checkout also offers USDT, you can instead send the exact amount it shows as USDT on TRON (TRC20); the order confirms itself about a minute after the transfer. Need a bank transfer and invoice instead? Contact us.

Do you get access to our source code?

No. Remendo Cloud stores the compiled patch files you upload so your players can download them, and nothing else. If that is still too much, run the server yourself.

What will it cost?

See pricing: per game per year, never per install. Design partners who help us with Android and iOS get early access free of charge.