AppXen Platform

What AppXen Platform is

AppXen Platform bundles four products and deploys them with a CloudFormation template as a single appliance in your account.

Everything runs on one instance, in your account, on your own Amazon Bedrock access. There is no AppXen-hosted service in the loop: you run and operate the appliance yourself, and AppXen does not host it or meter it.

Your data stays inside your AWS account. Every product talks to AWS (DynamoDB, S3, SQS, Bedrock, Textract) using the instance's own IAM role, never long-lived access keys, and secrets are generated locally on first boot and stored only on the instance. What the appliance connects to by itself, and what its IAM role can do, is listed in full under Network & IAM.

The appliance starts with a self-signed certificate, which browsers let you click through but MCP clients reject. Give it a domain of your own (at launch, or later with sudo appxenctl set-domain) before connecting clients.

Instance size. The appliance defaults to a t3.large (2 vCPU / 8 GiB), with the t3a.large and m6a.large AMD equivalents available as a cheaper option where your Region and Availability Zone offer them. That comfortably runs the full stack (five product services plus Postgres and Redis) for small-to-medium teams. Larger workloads should size up.

What the CloudFormation template creates

Launching the template builds the whole appliance in your own AWS account, in one stack:

• Its own VPC (10.0.0.0/16) with one public subnet (10.0.0.0/24, in the Availability Zone you choose), an Internet Gateway and a route table, so the stack has no dependency on any network you already have.
• One security group: HTTP and HTTPS open to the world, SSH restricted to the CIDR you supply.
• One EC2 instance running the AppXen Platform AMI, with an Elastic IP so its address survives a stop/start, an encrypted gp3 root volume, and IMDSv2 required.
• The data resources every product needs: five DynamoDB tables, three S3 buckets (media, RAG documents, backups) and an SQS queue with a dead-letter queue, all retained if you delete the stack (see Data retention below).
• One least-privilege IAM instance role (see IAM role), attached to the instance as an instance profile. The template creates no access keys: the platform's own AWS calls authenticate as this role.

The parameters you fill in are listed on the Deploy page.

Costs

You pay for the appliance's software through AWS Marketplace, at $0.149 per instance-hour or $949 per year on the large instance types, and $0.199 per instance-hour or $1,299 per year on the xlarge types (a single yearly charge in place of the hourly rate). You pay AWS separately for the infrastructure the template creates. Amazon Bedrock usage is extra and is billed by AWS to your account; it is not part of any figure below.

The default configuration (t3.large, us-east-1, priced 2026-09-29) runs about $178.88 a month before Bedrock usage at the hourly Marketplace rate, or about $149.19 a month at the annual rate. That covers the EC2 instance, its gp3 root volume and Elastic IP, the five DynamoDB tables, the three S3 buckets, the SQS queue pair, and the Marketplace software fee.

Infrastructure (billed by AWS)

Assumptions: the instance runs continuously (730 instance-hours in a 730-hour month), a 50 GiB gp3 root volume, one Elastic IP attached to the running instance, DynamoDB on-demand at 1,000,000 write requests and 5,000,000 read requests, 20 GiB in S3, and 1,000,000 SQS requests.

AMD alternative. Setting InstanceType to t3a.large instead ($0.0752/h x 730 h = $54.90) lowers the EC2 line and the subtotal by $5.84 a month, to $64.27. The default stays t3.large (the row above); see Parameters for the instance types and the one us-east-1 Availability Zone that offers none of them.

Marketplace software fee (billed by AWS Marketplace)

Totals, before Bedrock usage

The totals are for us-east-1 and a t3.large, priced on 2026-09-29; an xlarge type has the larger software fee above and a larger EC2 line. The EC2, EBS and public IPv4 prices carry an AWS-published effective date of 2026-09-01. Actual charges depend on your usage, your account's pricing agreements, and any AWS discounts you already have. This is an estimate, not a quote.

Amazon Bedrock

The appliance calls Amazon Bedrock in your account, so Bedrock usage is billed by AWS to you and is on top of either total above. Per-token prices for the models the appliance uses are not quoted here, because the AWS Price List API did not carry entries for Claude Haiku 4.5, Claude Sonnet 4.5 or Titan Text Embeddings V2 when these figures were priced. See the Amazon Bedrock pricing page and look up those models for your Region.

As a sizing reference, a light month of chat and RAG-embedding traffic (on the order of 1,000,000 input and 1,000,000 output tokens through the chat model, plus 10,000,000 tokens through the embeddings model) is typically a few dollars to a few tens of dollars a month at those two model families' published per-1,000-token rates. Heavier use scales linearly with tokens processed.

For your own instance type, Region and usage, enter the line items above in the AWS Pricing Calculator and add your Amazon Bedrock usage.

Regions

At launch, AppXen Platform is offered in US East (N. Virginia), us-east-1.

The appliance calls Amazon Bedrock in the same Region as the stack, so the models it uses need to be available to your account in that Region. See Before you launch: Amazon Bedrock model access.

Data retention

Deleting the stack does not delete your data. The five DynamoDB tables, the three S3 buckets and the SQS queue pair are all retained on stack deletion, by design, so a mistaken or accidental delete can never take your data with it. If you are done with the appliance for good, delete those retained resources yourself once you have confirmed you no longer need them.

Inside the buckets, a deleted or overwritten media file or RAG document, and an unshared output, stays recoverable as a noncurrent version for 30 days before S3 removes it. The parts of an interrupted upload are removed after 7 days. The backups bucket has its own lifecycle rules, described under Backups.

In this guide

For the product overview, see AppXen Platform.

Support

Email support@appxen.ai, or use the contact page.