Installing the beta
Downloading and installing a beta build of Amalgative Redline, what the 120-day expiry means, and how to report a bug so that it can be placed.
Amalgative Redline is in beta. It is incomplete, it will have defects, and it is not licensed for production work.
Work on copies. The file format may change between beta builds without a migration path. Never open your only copy of a file in a beta build.
Getting a build#
Builds are listed at amalgative.com/software/redline/.
Installing#
Linux#
Download the AppImage, make it executable and run it:
chmod +x Amalgative-Redline_*.AppImage
./Amalgative-Redline_*.AppImage
⚠ The AppImage updates itself — and so do the Windows installer and the macOS app. The .deb and .rpm packages are provided for people who prefer a system package, and they have no self-update path — update those through your package manager, or by downloading a newer build.
Windows#
The installer is not code-signed yet, so Windows Defender SmartScreen may stop it with “Windows protected your PC”: choose More info, then Run anyway. That warning appears until a build has been downloaded enough times to establish a reputation, and it is not a statement about the software.
Then right-click the installer, choose Run as administrator, and follow the installer.
macOS#
Open the .dmg and drag the application to Applications.
⚠ Apple silicon only (M1 and later). There is no Intel build, and a browser cannot tell the two apart — Safari reports "Intel" on both — so the download page says which one it is rather than guessing for you.
The application is signed with an Apple Developer ID and notarised by Apple, so it opens without the "unidentified developer" warning.
Builds expire#
Each beta build stops working about 120 days after the date it was released. This is deliberate: it stops a build from staying in use long after its problems were fixed, and it is stated in the licence agreement you accept on first run.
Amalgative Redline warns you as the date approaches and offers to update itself. If a build has already expired, it will still let you fetch a current one — and it shows a download address you can reach from another machine if it cannot.
Reporting a bug#
Use Help ▸ Report an Issue inside Amalgative Redline. It opens your mail client with the build identifier already filled in, which looks like this:
Amalgative Redline 0.5.0 B1 (a1b2c3d, 2026-09-14)
⚠ Please keep that line in the message. No licence keys are issued during the beta, so the identifier is the only thing that says which build you were running — and “it crashed when I opened a file” is a different bug in two different builds.
You can also write to support@amalgative.com.
Hearing about new builds#
Amalgative Redline checks for new builds itself — at launch and every four hours, unless you turn that off in Settings ▸ Updates. The optional list on the download page is for the times it cannot: a build that expired while you were away, or the beta programme ending.