Apex tests and Salesforce flows run on your developers' machines and on your CI runners, against an embedded database. New developers can run the full suite on their first day, and deploys are gated on the exact payload the tests passed against. No source or schema is sent to us.
Four open-source Apex suites, 837 tests, run once against a Salesforce org (deploy, then test) and once on renmy runtime. Every test passes in both. Org measured 2026-08-17, the local arm (release 1.45.0) on 2026-10-08.
A one-line trigger change means a push, a four-minute wait and then a failure caused by someone else's test data. Twenty minutes later you have debugged a problem that was not yours.
Day one: request org access. Day three: an admin provisions a sandbox. Day five: the first test run. Every new hire, on every project.
A JWT certificate, a connected org, a DevHub with scratch org limits, and an org pool that runs dry. The Java team next door has coverage badges that just work.
Enter your own numbers. Every figure on the right is arithmetic on the fields on the left, and the fields hold the whole model: there is no hidden multiplier. The numbers stay in your browser.
| Hours saved | Working day | Month | Year |
|---|---|---|---|
| Waiting on the org, per edit-test cycle | 1.8 h | 32 h | 385 h |
| Failures caused by shared test data | 0.7 h | 12 h | 147 h |
| New developers waiting for org access | 0.3 h | 5.3 h | 64 h |
| CI failures unrelated to the code | 0.1 h | 1.5 h | 18 h |
| Hours, total | 2.8 h | 51 h | 614 h |
| At $80 per hour | $223 | $4,091 | $49,093 |
| Team plan, 5 seats$245 per month, billed monthly | −$13 | −$245 | −$2,940 |
| Net | $210 | $3,846 | $46,153 |
The first row counts the whole cycle: if your developers get useful work done while the org deploys and runs tests, lower the minutes per cycle. Month is one twelfth of the year; working day is the year divided by the working days you entered. The Team plan price is the published one, before tax.
Your org stays the deployment target and the system of record. renmy runtime handles the steps that never needed an org.
Source-driven. Apex, triggers, flows and metadata in git.
The full suite, Apex and flows, on the CI runner. No connected org, no scratch org pool. Coverage and JUnit XML as artifacts.
Reviewers see the test results on the pull request itself.
Local gates, then a check-only validation of the same bytes in Salesforce. A signed receipt records what passed.
After approval, quick-deploys exactly the validated payload. Drift guard, promote and rollback.
Everything below is documented on the security page and in the DPA.
Read the security overviewApex source, schema and test data are read and executed locally, on the developer's laptop or your CI runner. Nothing is uploaded to us.
Running the suite needs no connected org, no JWT certificate and no sandbox. Org access is used only for validation and deployment, through the Salesforce CLI you already trust.
License validation and network behaviour are documented in full. Enterprise and air-gapped setups are covered on the security page.
DPA, subprocessor list, EULA and terms are published. Mutual NDA on request, yours or ours.
Assign and revoke seats, license a dedicated CI runner, and see who has what. Included in the Team plan.
Signed release receipts and the on-prem Assurance console give a durable record of what was validated and what was deployed.
Fixed prices, net, plus VAT. For businesses only (§ 14 BGB).
Full metadata pull, clean sfdx project layout, a git repository with history, and a team handover.
Every test class running locally, gap closure to the parity target, a CI pipeline template, and a written support map.
Up to about 20K lines of Apex, 200 test classes, single package, no managed-package dependencies.
20K to 100K lines, up to 1,000 test classes, multi-package, up to 2 managed-package stubs, CI for one platform.
100K+ lines, unlimited test classes, up to 5 managed-package stubs, CI for two platforms, dedicated Slack channel.
A service contract with Renmy UG (haftungsbeschränkt) i.G., under the consulting terms.
Book a setup callFor each Apex test, the same pass or fail result as running it against your production org. We run every test in both environments and diff the results. The target, typically 95%, is fixed in writing in the SOW.
We keep working at no additional cost until it is met; the engagement is not finished before then. Your statutory rights for defects are unaffected.
You do, once the fee is paid in full: the git repository, the migrated source, the CI configuration and every script produced for you, with an exclusive, transferable right to use them. Renmy UG keeps its own tools, libraries and templates, made independently of your engagement; where the work contains them, you may use them as part of it. renmy runtime itself is licensed under the plan you subscribe to. § 6 of the consulting terms sets this out.
No. Final validation and deployment happen in Salesforce, and anything a browser or an external system needs still happens in an org. Flows, approval processes and validation, duplicate, assignment and workflow rules run locally. renmy runtime removes the org from the steps where it was only slowing tests down.
Bring a test suite that is slow or flaky today. We will run it on the call and tell you what renmy runtime covers and what it does not.
Prefer email: sales@renmy.net
Already a customer: support@renmy.net