Pricing
Every plan on this page is rendered from the plan rows this deployment actually holds, so the prices and allowances below are the ones the service would apply - not figures typed into a page.
EngineerLM is in its test phase, and this page says so rather than pretending otherwise.
Usage metering is switched off on this deployment: nothing is being recorded and no allowance is being enforced. The numbers below are what each plan would grant once it is switched on. No payment provider is configured here, so nothing can be bought right now and no card is asked for anywhere. Any paid price below is a pricing hypothesis held as editable data, not a figure anyone has been charged.
No plans are published on this deployment
This installation has no plan rows yet, so there is nothing to quote
and no allowance applies. Prices and allowances are configuration, not
code: an administrator seeds them with
manage.py seed_plans, and this page will then show
whatever they hold.
What you get on either plan
- Every tool in the catalog, at the same versions - plans differ by how much you may run, never by which calculations are available.
- Chat, the REST engineering API and
MCP, on one identity and one set
of
elm-keys. - Stored, exportable calculation records with per-step provenance.
- Bring your own OpenAI or OpenRouter key if you would rather not use the shared model. Those conversations are not metered.
Ready to start?
Signing in with Google creates your account. Access to chat, the API and MCP is switched on once an administrator approves it, so you may wait a little before your first calculation. No card is asked for at any point.