Nimbus is now renmy runtime
Nimbus, the local Apex runtime, now goes by renmy runtime. Nothing you have installed stops working, and there is nothing you need to do.
Why the name changed
Nimbus is a registered trademark held by other companies for software in the European Union, including in Germany, where this is built. renmy is our own name.
Say it “ren-MY”, like “run my”: renmy runs your Apex tests, flows and deploys on your machine, with no org.
What keeps working
Everything keeps working. The rename adds the new spelling beside the old one rather than replacing it, and the old one is supported for good.
| What | Status |
|---|---|
The nimbus command | An install puts both renmy and nimbus on your machine, running the same binary. Scripts, aliases and muscle memory are unaffected. |
NIMBUS_* environment variables | Every one of them is still read. RENMY_* is accepted too, and wins when both are set. |
nimbus.properties and its nimbus.* keys | Read exactly as before. renmy.properties and renmy.* keys are also read, and a project with both loads both. |
The .nimbus directory in your project | Same name, same contents: the database, traces, coverage, history and schemas all stay where they are. |
The ~/.nimbus directory in your home | Same name. Your licence, your machine activation and the PostgreSQL template are untouched, so nothing re-downloads and nobody is signed out. |
nimbus upgrade | Installs the current release as it always has, including from a build published before the rename. |
brew upgrade nimbus | Migrates you to the renamed formula and leaves the nimbus command in place. |
scoop update nimbus | Unchanged. Both manifests are published. |
| The VS Code and JetBrains plugins | Update in place under the extensions you already have installed, keeping your settings, keybindings and run configurations. |
sf nimbus … | Still works, in the Salesforce CLI plugin you already have. |
uses: nimbus-solution/setup-nimbus@v1 | Keeps working in your CI files: GitHub forwards the old organisation name to renmy-solutions, where the action now lives. |
What changed
The product name changed, and with it this website and its address, the command the documentation teaches and the names shown in your editor. The binary answers to whichever name you type, so the documentation saying renmy test and your terminal history saying nimbus test are the same command.
From , renmy runtime is made by Renmy UG (haftungsbeschränkt) i.G..
One thing deliberately did not change: a project without a settings file still gets nimbus.properties. A colleague running a release from before the rename cannot read a file named renmy.properties, and settings that are silently ignored are worse than a filename that looks dated.
If you would rather not be reminded
The CLI mentions the rename a few times when you invoke it as nimbus, then stops. To silence it immediately, set RENMY_NO_RENAME_NOTICE=1.