Everything Elements does today is in the free beta. Two paid plans are planned for afterwards, for more throughput and for teams. Their prices are below so you know what to expect.
Free beta
Available now
$0
The whole product, with no card and no features held back.
Rehearsal, approvals, replay, tests and shadow runs
Sheets, impact preview, answer sources and proposed fixes
Deploy as a REST endpoint and an MCP tool
Webhook and schedule triggers
API keys scoped to a deployment, each with its own rate limit
Encrypted credential vault
Python SDK and REST API
30 days of run history
Basic
Planned
$19per month
For one person running pipelines in production who needs more throughput and a longer record.
Opens after the beta. Beta accounts are told first.
Everything in the free beta, and:
Higher rate limits on runs and deployments
50 saved pipelines and 10 deployed endpoints
90 days of run history
Audit log export
Email support
Pro
Planned
$49per month
For teams: shared workspaces, roles, and models that run on your own hardware.
Opens after Basic. None of this is built yet.
Everything in Basic, and:
No cap on pipelines, deployments or API keys
Organizations and team workspaces
Roles: owner, admin, member, viewer
Custom domain for endpoints
Single sign-on and two-factor sign-in
Local Gemma and self-hosted vLLM as model providers
Custom step builder
Priority support
What is in each plan
Feature
Free beta
Basic
Pro
Building
Step types
All 70
All 70
All 70
Retrieval strategies
All 9
All 9
All 9
Use cases and templates
6 and 17
Yes
Yes
Saved pipelines
No cap in the beta
50
No cap
Custom step builder
Not included
Not included
Planned
Running
Runs per minute
30
120
600
Longest run
300 seconds
300 seconds
300 seconds
Run history kept
30 days
90 days
No expiry
Branching, retries, fallbacks and loops
Yes
Yes
Yes
Testing and release
Rehearsal, fire drill and replay
Yes
Yes
Yes
Human approval steps
Yes
Yes
Yes
Tests that gate a deploy
Yes
Yes
Yes
Shadow runs and rollback
Yes
Yes
Yes
Signed receipts
Yes
Yes
Yes
Working on many runs
Sheets
Yes
Yes
Yes
Impact preview before a deploy
Yes
Yes
Yes
Answer sources
Yes
Yes
Yes
Proposed fixes for failing deployments
Yes
Yes
Yes
Search for cheaper models
Yes
Yes
Yes
Deploying
REST endpoints
No cap in the beta
10
No cap
MCP tool
Yes
Yes
Yes
API keys scoped to a deployment
Yes
Yes
Yes
Webhook and schedule triggers
Yes
Yes
Yes
Custom domain
Not included
Not included
Planned
Models
OpenAI, Anthropic, Gemini, Groq, OpenRouter
Yes
Yes
Yes
Local Gemma
Not included
Not included
Planned
Self-hosted vLLM
Not included
Not included
Planned
Security and teams
Encrypted credential vault
Yes
Yes
Yes
Audit log export
Not included
Planned
Planned
Organizations and roles
Not included
Not included
Planned
Single sign-on
Not included
Not included
Planned
Two-factor sign-in
Not included
Not included
Planned
Support
Support
Community
Email
Priority
The free beta column is what the server does now. Basic and Pro are plans and may change before they open.
Questions
Is the beta really free?
Yes. There is no charge and no card. Every step type, every retrieval strategy, deployment, the SDK and the tools on this page are included.
What are the limits today?
By default a server allows 30 runs a minute, stops a run after 300 seconds, and keeps run history for 30 days. There is no cap on saved pipelines or deployments during the beta. If you host Elements yourself, these are settings you can change.
Can I buy Basic or Pro now?
No. They are plans for after the beta, and the prices shown are the intended ones. Basic adds throughput and a longer record. Pro is for teams, and its features are not built yet.
Will my work carry over?
Yes. Pipelines, credentials, deployments and run history stay with your account when paid plans open. Beta accounts are told first and keep beta pricing for the first year.
How are my provider keys protected?
Keys saved to the vault are encrypted with AES-256-GCM and used by name inside a pipeline. The API never returns a decrypted key.
Can I run it on my own machines?
Yes. Elements is self-hosted: the studio, the API and the databases run where you put them, and your documents and run history stay there.