Retrojet Docs

What is Retrojet

Mon, 01 Jan 0001 00:00:00 +0000

Retrojet lets you fix a Flutter app that is already in your users’ hands, without shipping a new build through the App Store or Google Play and waiting for review.

You publish a release through the store as usual, and Retrojet keeps a copy of it. When you change Dart code later, the Retrojet CLI builds a patch for that release and uploads it. Devices that run the release download the patch and use it the next time the app starts.

About Retrojet

Mon, 01 Jan 0001 00:00:00 +0000

Why

A one-line fix in a Flutter app can take days to reach users: build, submit, wait for review, wait for users to update. Retrojet shortens that path for Dart changes. You still ship releases through the stores, and between releases you send patches straight to the devices that run them.

How it is built

Part	Built with	Role
CLI	Go, one static binary per OS	Sign-in, project setup, building and uploading releases and patches
Backend	Java, Spring Boot, PostgreSQL	Accounts, organizations, apps, releases, patches, channels, usage
Console	Next.js, React, Tailwind CSS	The web app your team uses to check, promote, and roll back
These docs	Hugo with the Lotus Docs theme	Static pages, no server code

Rules we keep

The CLI creates, the console controls. Releases and patches are only made from the CLI, where the build happens. The console can promote, roll back, and delete, so a browser is enough to react when something breaks.
Rollback is per channel. Stopping a patch for testers never touches what your users on stable run.
Tokens stay out of the browser. CLI sign-in uses PKCE, so the token goes straight from Retrojet to your terminal. The console keeps your access token encrypted in an HttpOnly cookie that page scripts cannot read.
Patches are signed. Every patch file is uploaded with a signature.
Honest docs. If something is not available yet, the page says so.

Status

Retrojet is in early access. The console, sign-in, and project setup work today. Building releases and patches from the CLI is in progress. See What is Retrojet for the current state.

Install the CLI

Mon, 01 Jan 0001 00:00:00 +0000

The Retrojet CLI is a single file. Put the binary for your system somewhere on your PATH and you are done.

Pick your binary

File	System
`retrojet-darwin-arm64`	macOS on Apple silicon (M1 and later)
`retrojet-darwin-amd64`	macOS on Intel
`retrojet-linux-amd64`	Linux x86_64
`retrojet-linux-arm64`	Linux ARM64, for example Graviton or a 64-bit Raspberry Pi
`retrojet-windows-amd64.exe`	Windows x86_64

Each release also ships a checksums.txt with the SHA-256 of every file, so you can check that a download is complete and unchanged:

Concepts

Mon, 01 Jan 0001 00:00:00 +0000

 Organization
└── App one per package ID, e.g. com.acme.demoapp
 ├── Channels stable (always there), staging, beta, …
 └── Releases 1.4.0+12, 1.5.0+13, …
 └── Patches 1, 2, 3, … each published to one or more channels

Organization

Everything in Retrojet belongs to an organization. Signing up creates one for you, and you are its Owner. Other organizations can add you as a member, so one account can work in several.

License

Mon, 01 Jan 0001 00:00:00 +0000

Retrojet

The Retrojet CLI, backend, console, and these docs are proprietary software. You may use the CLI and the console to work with your own Retrojet account. Copying, modifying, redistributing, or reselling them is not allowed without written permission.

Open source software

Retrojet is built on open source projects. Each keeps its own license, and nothing on this page changes those terms.

Quickstart

Mon, 01 Jan 0001 00:00:00 +0000

You need the CLI installed and a Flutter project. If you do not have a Retrojet account yet, the sign-in step lets you create one.

 retrojet login

Your browser opens the Retrojet console. Sign in (or create an account), check that the request comes from your terminal, and click Allow. Back in the terminal you see:

 ✓ Logged in to Retrojet.
 Patch your Flutter apps in minutes, not days.

Working over SSH or on a machine without a browser? Use retrojet login --no-browser and open the printed URL on any device. Check who you are signed in as with retrojet whoami.

CLI reference

Mon, 01 Jan 0001 00:00:00 +0000

 retrojet <command> [flags]

Run retrojet --help or retrojet <command> --help for the same information in your terminal.

Signs the CLI in to your Retrojet account through the browser.

 retrojet login
retrojet login --no-browser # only print the URL, open it yourself

Flag	Meaning
`--no-browser`	Do not open a browser. Useful over SSH or on a machine without a desktop.

What happens:

The CLI starts a small server on 127.0.0.1 and opens the console at https://retrojetdev.cloud/cli/login. The URL is also printed, in case the browser does not open.
You sign in if needed, then click Allow. Cancel stops the login.
The browser hands a one-time code back to the CLI, which exchanges it for an access token directly with Retrojet.

The access token never passes through the browser. The login uses PKCE (RFC 7636), so a code that leaks from the browser history is useless on its own. It expires after 5 minutes and works only once.

Console

Mon, 01 Jan 0001 00:00:00 +0000

The console lives at retrojetdev.cloud. Sign up with email and password or with Google. The interface is available in English and Bahasa Indonesia; switch from the sign-in page or the header.

Plans and limits

Mon, 01 Jan 0001 00:00:00 +0000

	Free	Pro	Enterprise
Apps	1	Unlimited	Unlimited
Patches published per month	10	Unlimited	Unlimited
Adding members	No	Yes	Yes
Patch installs and devices	Unlimited	Unlimited	Unlimited

info

Upgrading from the console is not available yet. Contact the Retrojet team to change the plan of your organization.

How usage is counted

Apps is the number of apps right now. Deleting an app frees its slot.
Patches published counts each publish this month, in UTC, and resets on the first day of the month.
- Draft patches do not count.
- Promoting a patch to another channel does not count.
- Deleting a release does not give the count back.
Patch installs and devices come from the reports your app sends. They are shown for information and never limited. Reports from deleted apps are not counted.

When you reach a limit

Limit	What you see
Second app on Free	`Upgrade your plan to add more apps`. The console disables Create app.
11th publish in a month on Free	`Monthly patch limit reached; upgrade your plan to publish more patches`
Adding a member on Free	`Upgrade your plan to add members`. The console explains this instead of showing Add member.

Changing roles and removing members works on every plan.

Retrojet Docs

What is Retrojet

About Retrojet

Why link

How it is built link

Rules we keep link

Status link

Install the CLI

Pick your binary link

Concepts

Organization link

License

Retrojet link

Open source software link

Quickstart

1. Sign in link

CLI reference

retrojet login link

Console

Plans and limits

How usage is counted link

When you reach a limit link

Why

How it is built

Rules we keep

Status

Pick your binary

Organization

Retrojet

Open source software

1. Sign in

retrojet login

How usage is counted

When you reach a limit