Pricing & Licensing

In-account pricing that matches how cloud teams buy software

Clear pricing. No surprises.

Pricing follows a simple model: your data stays in your account, you pay infrastructure directly (AWS at launch), and we license/support the platform backbone.

  • Scaffold deployed in under an hour — once kickoff inputs and approvals are in place.
  • First tailored enterprise agent delivered in 2–8 weeks (integrations/scope).
Deployed in your AWS account You pay AWS directly Security-first defaults

We’ll map your environment and use cases to a clear estimate—highlighting the biggest infrastructure cost drivers and where to optimize (AWS at launch).

How it works

Simple model: infrastructure + subscription + (optional) implementation

Pricing is straightforward: infrastructure (paid to your cloud provider—AWS at launch) + The Agent Within subscription (the backbone) + an implementation engagement if you want us to deliver tailored agents and integrations.

AWS infrastructure (paid to AWS)

You continue to pay AWS directly for EC2, Aurora/RDS, S3, Bedrock, and other usage in your account.

  • Total cost depends on traffic, documents, model choice, and runtime sizing.
  • We’ll guide you on expected ranges for common patterns.

The Agent Within software subscription

Recurring monthly or yearly fee for the platform backbone: auth, UI, RAG wiring, agent runtime patterns, observability, updates, and base support.

  • Includes updates and bug fixes to maintained components.
  • Designed for adding more agents over time without platform rebuilds.

Professional services & advanced features

If you want us to deliver tailored agents and integrations (typically 2–8 weeks), we scope it as project work or package it into higher tiers.

  • Custom agents + integrations (CRMs, ERPs, ticketing, internal APIs).
  • Advanced scaling/HA, evaluation, guardrails, orchestration.

For what’s possible, see the Product extensions.

AWS costs

Estimate infrastructure costs on AWS

AWS usage is billed by AWS to your account. Use the links below to sanity-check costs and build an estimate quickly.

Core scaffold services

Click a service to open AWS pricing/docs in a new tab.

Use the AWS Pricing Calculator for your most accurate estimate.

What we’ll ask for (to estimate AWS costs)

AWS’s calculator is service-by-service. This helps you capture the few inputs that most affect your spend, so your team (or we) can build a no-surprises estimate quickly.

  • Users & volume: monthly users, avg chats/user, peak concurrency
  • Model usage: model(s), avg tokens per chat, % of chats using RAG
  • Data: document count/GB, update frequency, retention
  • Runtime: desired latency, region, HA needs (single-AZ vs multi-AZ)

If you want, we’ll turn this into an AWS Pricing Calculator estimate with you.

Tiers

Tiers at a glance

These are scope guidelines, not rigid bundles. Exact pricing depends on your environment and use cases.

Starter

1 environment • core scaffold • 1 tailored agent

  • Single environment (AWS account / VPC at launch).
  • Initial agent focused on one area (knowledge assistant or support copilot).
  • Best for pilots and single-team rollouts.

Growth

Multiple agents/departments • custom workflows

  • Core scaffold used across departments (HR, Support, Ops).
  • Mix of proven patterns + select custom integrations.
  • Best for expanding beyond pilot with manageable complexity.

Enterprise

Advanced safety • scaling/HA • priority support

  • Org-wide usage with higher-stakes workloads.
  • Advanced governance/guardrails + scaling/availability options.
  • Best for complex workflows and strict risk posture.

If you’re unsure, we usually start with a Starter- or Growth-style scope and expand as usage grows.

FAQ

Common questions

Next step

Get a pricing estimate

Pricing is most accurate when tied to your real-world environment, use cases, and internal capacity (AWS at launch). Share your setup and we’ll come back with a tailored estimate and deployment plan.

  • Your environment footprint (accounts, regions, existing services — AWS at launch).
  • Initial use cases and expected traffic.
  • How much you want us to build vs. your team.