Pricing
Pricing for Ramain SaaS and Enterprise deployments, separated by commercial model, billing unit, infrastructure ownership, and support motion.
Ramain has two commercial models. SaaS is the hosted product with transparent Agent Hour pricing. Enterprise is a private deployment or on-prem / Private VPC deal with outcome-based pricing, implementation scope, and customer-controlled infrastructure.
Choose the right model
| Question | SaaS | Enterprise |
|---|---|---|
| Where does it run? | Ramain-hosted multi-tenant cloud | Customer-controlled Private VPC, on-prem, or dedicated cloud |
| Best for | Fast start, standard data residency, predictable automation usage | Data sovereignty, private networking, procurement controls, dedicated deployment |
| Commercial unit | Agent Hour | Annual platform license + implementation fee + event / outcome usage |
| Public rate | $10 / Agent Hour committed · $12 / Agent Hour on-demand | Custom, based on deployment model, annual platform scope, event definition, annual volume, and support tier |
| Commitment | 50 Agent Hours per agent per month | Semi-annual or annual order form |
| Infrastructure costs | Included in SaaS rate | Customer pays cloud / infrastructure costs directly |
| Implementation | Standard onboarding | Scoped deployment, access, security, integration, and cutover plan |
Same product, different buying motion
SaaS and Enterprise run the same Ramain automation platform. The difference is not capability. The difference is who operates the infrastructure, how usage is metered, how procurement works, and how much deployment control the customer needs.
SaaS Pricing
SaaS is for teams that want Ramain hosted and operated by us. You buy a shared monthly or quarterly pool of Agent Hours, then deploy agents against that pool.
SaaS unit: Agent Hour
Agent Hour
One hour of an autonomous Ramain agent doing production work: clicking, looking up records, filling forms, validating outputs, retrying failures, and returning completed results.
Committed SaaS rate — $10 / Agent Hour
Best for steady production usage. Commit to a monthly or quarterly pool and lock in the lower rate.
On-demand SaaS rate — $12 / Agent Hour
Used when you exceed the committed pool or want burst capacity without increasing the committed baseline.
SaaS commitment model
| SaaS item | Detail |
|---|---|
| Base unit | Agent Hour |
| Committed rate | $10 / Agent Hour |
| On-demand burst rate | $12 / Agent Hour |
| Minimum guarantee | 50 Agent Hours per agent per month |
| Billing cadence | Monthly or quarterly |
| Pooling | Hours are fungible across all agents on the account |
| Rollover | Unused committed hours roll forward while the MGA remains active |
| Infrastructure | Included in the SaaS price |
How SaaS pooling works
Pick how many agents you want live. Each production agent carries a 50 Agent Hour monthly minimum guarantee.
The committed hours go into one account-wide pool. Three agents create a 150 Agent Hour monthly pool.
Any agent can use the pool. One agent can run 100 hours while another uses 20. We bill against the total pool, not isolated per-agent buckets.
Burst above the pool at the on-demand rate. If a month spikes beyond committed hours, the excess is billed at $12 / Agent Hour.
SaaS example — 3 agents, 150-hour pool
- Payer portal agent — 20 hours used
- Eligibility agent — 30 hours used
- Claims agent — 100 hours used
Total usage is 150 Agent Hours, so the entire month is covered by the committed SaaS pool at $10 / Agent Hour.
SaaS invoice examples
One production agent — $500 / month
1 agent × 50 Agent Hour MGA × $10 / Agent Hour = $500 monthly committed SaaS spend.
Three production agents — $1,500 / month
3 agents × 50 Agent Hours each = 150 committed Agent Hours. At $10 / Agent Hour, the monthly committed SaaS spend is $1,500.
Three agents with a burst month — $2,100
150 committed hours cost $1,500. A 50-hour burst above the pool costs $600 at $12 / Agent Hour. Total: $2,100 for that month.
SaaS volume discounts
Volume discounts apply to annual pre-committed Agent Hour pools. Tier breakpoints are evaluated at contract signing.
| Annual committed hours | Discount | Effective SaaS rate |
|---|---|---|
| 1,000+ Agent Hours / year | 10% | $9.00 / Agent Hour |
| 2,500+ Agent Hours / year | 15% | $8.50 / Agent Hour |
| 5,000+ Agent Hours / year | 20% | $8.00 / Agent Hour |
Why one Agent Hour is not one human hour
1 Agent Hour often replaces 1.5–2 human hours because the agent does not context-switch, take breaks, wait for office hours, or re-learn a repetitive portal flow.
| Example | Human team | Ramain SaaS |
|---|---|---|
| 30 prior-auth lookups | ~90 minutes of manual portal work | ~50 minutes of agent runtime |
| Coverage | Office hours, overtime, staffing constraints | Nights, weekends, and holidays at the same Agent Hour rate |
| Billing unit | Payroll time | Agent Hours consumed from your pool |
Enterprise Pricing
Enterprise is for customers who need Ramain deployed into their own environment or require a private commercial structure. Enterprise pricing is not an hourly SaaS meter. It has three separate commercial lines: a one-time implementation fee, a yearly platform license fee, and event / outcome usage pricing.
Enterprise price components
| Component | What it covers | Billing |
|---|---|---|
| Implementation fee | Deployment planning, environment provisioning, identity / RBAC, target-system access, connector setup, validation, and cutover | One-time, scoped in the order form |
| Platform license fee | The right to run the Ramain platform in the private environment, product updates, core platform maintenance, security patches, and account-level platform support | Annual license |
| Event / outcome usage | Business outcomes completed by agents, such as claims filed, lookups returned, forms submitted, or records retrieved | Semi-annual or annual usage commitment / true-up, as defined in the order form |
Enterprise invoices separate platform from usage
The annual platform license is not the same as usage. The license covers access to and maintenance of the private Ramain platform. Event pricing covers the business outcomes the agents produce on top of that platform.
Enterprise unit: Event
An Event is the completed business outcome the agent produces. The event definition is written into the order form so pricing maps to the value delivered, not just time spent running.
Per claim filed
A claim submitted to a payer, clearinghouse, or portal and accepted at intake.
Per eligibility lookup
A payer portal lookup completed and returned with normalized eligibility information.
Per prior-auth status check
A status check performed, interpreted, and returned to the customer system.
Per EHR record retrieved
A patient or chart record accessed, normalized, and returned to the workflow.
Per government or provider form filed
A regulated form or provider-portal entry submitted with confirmation.
Enterprise commercial model
| Enterprise item | Detail |
|---|---|
| Platform license | Annual fee for the private Ramain platform |
| Implementation fee | One-time scoped deployment and onboarding fee |
| Usage unit | Event / completed outcome |
| Usage rate | Custom, based on event type, annual volume, deployment model, and support tier |
| Billing cadence | Semi-annual or annual |
| Infrastructure | Customer pays AWS, GCP, Azure, or on-prem costs directly |
| Deployment | Private VPC, customer-owned cloud account, dedicated cloud, or on-prem |
| Support | Business or Mission-critical SLA recommended |
| Contracting | MSA + order form with event definitions and volume assumptions |
Why Enterprise is priced differently
Enterprise deployments have cost and responsibility lines that SaaS does not:
- Infrastructure is customer-controlled. The customer usually pays cloud bills directly and owns networking, account guardrails, and observability requirements.
- Implementation is deeper. Private networking, identity, service accounts, security review, portal access, and cutover are scoped up front.
- The platform is licensed annually. Enterprise customers license the private Ramain platform separately from usage so the baseline platform, maintenance, updates, and support are covered even before event volume scales.
- Usage maps to business outcomes. Enterprise buyers often prefer price per claim, lookup, record, or filing because it ties directly to business volume.
- Support is production-critical. Dedicated Slack, named escalation paths, and tighter SLAs are usually part of the package.
Enterprise example — mid-market payer
Three workflows across two regions: eligibility lookups, prior-auth submissions and claim-status checks, deployed in the customer's own VPC. Volume below is illustrative; your actual rate is set in the order form.
| Event type | Volume / mo | Rate | Subtotal |
|---|---|---|---|
| Eligibility lookup | 40,000 | illustrative | $X |
| Prior-auth submission | 8,000 | illustrative | $Y |
| Claim-status check | 25,000 | illustrative | $Z |
| Total monthly events | 73,000 | — | contact sales |
Enterprise implementation timeline
Typical private deployments take 2–4 weeks when access is ready. Scope includes environment provisioning, identity / RBAC setup, service accounts, portal access, connector configuration, security validation, dry runs, and production cutover.
Enterprise infrastructure costs
Enterprise customers pay infrastructure directly unless the order form states otherwise. This can include compute, databases, storage, logs, inference, browser automation runtime, NAT / egress, and monitoring.
See Infrastructure Cost Model for the deployment-side cost categories.
Enterprise invoice structure
An Enterprise order form normally separates:
- One-time implementation fee — paid once for deployment and onboarding.
- Annual platform license — billed yearly for the private platform.
- Event / outcome pricing — billed against committed or actual business volume, depending on the order form.
Support and SLAs
Support is available for both SaaS and Enterprise. Business or Mission-critical SLAs are most common for production Enterprise deployments.
Standard — included · 99.5% uptime
Email support during US Pacific business hours. Right fit for non-critical and back-office workflows. P1 / P2 response 4 business hrs · P3 1 business day · Email · Mon–Fri PT.
Business — enterprise default · 99.9% uptime
Dedicated Slack channel and email. P1s answered 24/7 by an on-call engineer. Default for production deployments. P1 1 hr 24/7 · P2 4 business hrs · P3 1 business day · Slack + email · P1 24/7, rest M–F PT.
Mission-critical — purchaseable · 99.95% uptime
For workflows where downtime moves dollars. Faster P1, named TAM, quarterly review and DR rehearsal. P1 30 min 24/7 · P2 2 business hrs · P3 4 business hrs · Slack + named TAM · 24/7 across severities.
What's included
The exact included scope depends on SaaS vs Enterprise, but the principle is the same: we do not nickel-and-dime core platform work required to make Ramain successful.
SaaS includes hosting
Ramain operates the platform, infrastructure, upgrades, monitoring, and standard security controls.
Enterprise includes deployment scope
Private deployment planning, environment setup, access validation, and cutover support are scoped in the implementation.
Workflow buildout
Portal connectors, workflow configuration, prompt tuning, validation, and iteration are included in the commercial scope.
Compliance evidence
SOC 2, ISO 27001, BAA, DPA, sub-processor list, and security documentation are available through the trust portal.
Training and enablement
Operator onboarding, runbooks, and refresher sessions for the teams using the agents.
Customer success
Named commercial and technical contacts for onboarding, expansion planning, and quarterly business reviews.
Need a quote?
- SaaS pricing — founders@ramain.ai · Agent Hour pools, MGA sizing, volume discounts
- Enterprise pricing — founders@ramain.ai · Private deployment scope, event definitions, annual volume assumptions
- Legal & MSA — legal@ramain.ai · Master Subscription Agreement, order forms, DPAs
- Trust portal — trust.ramain.ai · SOC 2, ISO 27001, sub-processors, security whitepaper