Access is granted, not bought
An administrator creates the account and sets how long its access runs for. Trial and renewal windows are configuration, set per installation.
Pricing
How access works
Plans and prices are not published yet. JMXPress has no billing in it today — there is no payment integration and no plan stored against an account — so rather than show figures that are not real, this page shows how access actually works and leaves the rest to a conversation.
No billing is built into JMXPress today
There is no payment integration, and no plan is stored against an account. An administrator creates accounts and sets how long their access runs for; the trial and renewal windows are configuration on each installation. Anything resembling a price on this page would be a guess, so there is none.
One installation, your machines
JMXPress runs on a server you control, against a PostgreSQL database you control. What it costs to run is what that machine costs.
Talk to us about your team
How many testers, how many load generators, which APM you already have. That conversation is more useful than a table.
What a team gets
One installation, everything in it. There are no features held back behind a tier that does not exist.
Team
Talk to us
For a performance testing team running against their own applications.
- The whole workbench — recording, conversion, execution and reports
- Distributed load generation across your own machines
- APM monitoring against the provider you already use
- Diagnostics from machines you have enabled them on
What it costs to run
JMXPress runs on a server you control, against a PostgreSQL database you control, generating load from machines you control. There is no metered service in the middle, and nothing is sent anywhere else — your APM credentials stay on your own installation.