aer runs Apex on your machine — tests, classes, triggers, the whole suite — with no org and no deploy. A 90-minute Salesforce run finishes in under five minutes, so changes reach production faster.
Coding agents generate Apex faster than any team can review it — but every class, every test, every fix still has to reach an org before anyone knows it works. The deploy-and-test loop that already slowed your developers is now the bottleneck for your agents as well, with more code than ever queued behind the same slow round-trip.
Push to org, wait, refresh, repeat. The context switch kills momentum on every change.
What should be instant becomes a waiting game. Engineers stop running tests, and quality slips.
AI writes Apex in seconds, then waits minutes for an org to prove it works. Generation got fast; verification didn't.
aer is a local Apex runtime built for speed, clarity, and modern workflows. It runs your code — tests, classes, triggers — without touching an org, and executes it the way Salesforce does. It's production-grade infrastructure built for real codebases with hundreds of classes, by people who write Apex every day.
It's the same language and the same semantics, with feedback that lands in seconds.
Execute production code on your dev machine with zero network overhead. Work offline; own your environment.
Validation in milliseconds, not minutes. Run your entire suite as fast as you can type.
Schema-aware, trigger-respecting, governor-limit-enforcing. Real Apex behavior — just faster.
These are timings from production codebases, measured end to end. The bigger and slower your suite is today, the more time aer gives back to every developer, every day.
Timings from customer suites. Your results depend on suite shape, DML volume, and hardware.
When verification is instant, developers run tests while they write code, well before a commit reaches CI. Bugs surface earlier, reviews move faster, and the path from idea to deploy gets dramatically shorter.
Optional viewing — pick the one that sounds like your team. Each opens in a new tab.
aer meets your team in their editor — no new workflow to adopt. Set breakpoints, step through execution, and run the suite without leaving the IDE.
A real VS Code editor in your browser — run a failing test, set a breakpoint, and step through Apex live, all powered by aer.
Run and debug tests from inside VS Code. Real breakpoints, live variables, and call stacks — line-by-line execution control for Apex.
View on the VS Code Marketplace ↗Already on Illuminated Cloud in JetBrains IDEs? aer plugs in directly, so your team keeps the toolchain they know and gains local speed underneath.
A drop-in sf plugin runs your tests in aer instead of an org — ideal for CI and existing scripts.
aer behaves like the Salesforce Apex runtime, executing against an embedded database seeded from your metadata. The parts of Apex that normally need an org work locally — so your real tests run, unmodified.
An embedded database seeded from your metadata, queried and mutated like the real thing.
Automation fires alongside your Apex on every DML, exactly as it does in an org.
Tracked and enforced, raising the same LimitException you'd hit in production.
The platform namespaces and built-ins your code already depends on.
The full test harness, including coverage output your CI can consume.
Running tests parse- and type-checks your code, catching errors before you deploy.
Download aer and start running tests today — no signup, no org, no procurement. Suites of up to 100 tests and short debugger sessions are free. Start a trial for a license key when you want to run your whole suite at once and debug without limits.
Everything you need to try aer for real.
Start a trial to unlock it in minutes.
Enter your email — no card required to evaluate.
Retrieve it from the aer license portal.
Developers register for licenses with the key.
Seats, your CI license & billing in one portal.
Your team can install aer and run tests today — free, no trial. Start a trial only when you need a license key.
Install aer, run your first suite in milliseconds, and feel the difference immediately. Then hand it to your team.