Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.emergence.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
AWS Marketplace

CRAFT is available on the AWS Marketplace as a Container Product. Customers can deploy the platform into their own EKS clusters and apply purchases against their AWS Enterprise Discount Program (EDP) commitments.

​
Why AWS Marketplace

EDP Drawdown

Customers apply CRAFT purchases against their AWS Enterprise Discount Program (EDP) commitments, removing budget approval friction.

Co-Sell with AWS

Private offers enable AWS field teams to co-sell, earning quota credit and aligning sales incentives.

Larger Deals

Marketplace-transacted deals are 112% larger on average than direct sales, according to industry research.

Low Fees

3% fee for contract-based pricing, 1.5-3% for private offers. Contract-based pricing is recommended to avoid higher hourly/monthly fees.

​
Architecture

CRAFT’s cloud-agnostic Helm chart deploys the same platform services on EKS as on GKE. The AWS-specific work is scoped to infrastructure modules and marketplace packaging:
ComponentSource
Application chartem-runtime Helm chart (cloud-agnostic)
Infrastructure moduleEKS Terraform module (to be built as part of marketplace strategy)
Container imagesPublished to Amazon ECR via CI/CD multi-registry pipeline
Marketplace packagingContainer product with Helm charts and container images

​
Deployment Model

Private offers are managed through the AWS Marketplace Management Portal (AMMP).
1

Create a private offer in AMMP

The sales team configures pricing using contract-based pricing (recommended) with custom dimensions and generates a private offer for the target customer.
2

Customer accepts the offer

The customer receives the private offer link, reviews pricing and EULA terms, and subscribes through their AWS Console. Charges apply against their EDP commitment.
3

Deploy to EKS

After subscription, deploy the platform into the customer’s EKS cluster using the Terraform module and Helm chart provided with the listing.

​
Billing Integration

AWS billing uses the MeterUsage and RegisterUsage APIs for consumption tracking.

​
Pricing Model

AWS Marketplace requires contract-based pricing for the most favorable fee structure:
ModelFeeMechanism
Contract3%Customer commits to a term (monthly/annual)
Contract + Consumption3% base + usageContract base plus metered overage via MeterUsage API
Private Offer1.5-3%Custom pricing per customer

​
Metered Dimensions

DimensionUnitAPI
agents_registeredcountMeterUsage
api_requestscountMeterUsage
data_transfer_out_gbGBMeterUsage
health_checkscountMeterUsage
AWS enforces stricter dimension naming conventions than GCP or Azure. Dimension names must use snake_case and match exactly between the listing definition and the metering API calls.

​
Container Image Publishing

The CI/CD pipeline publishes images to Amazon ECR as part of the multi-registry strategy: 
# ci-main.yml excerpt
- name: Push to ECR
  run: |
    aws ecr get-login-password --region us-east-1 | \
      docker login --username AWS --password-stdin $ECR_REGISTRY
    docker tag emergence/governance:$VERSION $ECR_REGISTRY/emergence/governance:$VERSION
    docker push $ECR_REGISTRY/emergence/governance:$VERSION
The following images are published:
  • 3 production services (Governance, Assets, Utils)
  • 5 subchart images (Keycloak, OpenFGA, PostgreSQL, Redis, Infisical (or ESO))
  • 4 init container images (schema migration, bootstrap, health-check, seed data)

​
Prerequisites for Deployment

Before deploying from AWS Marketplace:
  1. EKS cluster — An existing EKS cluster (1.28+) with managed node groups or Fargate profiles
  2. Amazon RDS — PostgreSQL 17+ instance with 9 databases
  3. ElastiCache — Redis 7 cluster for caching and event streaming
  4. IAM — IRSA (IAM Roles for Service Accounts) configured for service-to-AWS authentication
  5. Networking — VPC with private subnets and security groups allowing cluster-to-database connectivity

​
Comparison with GCP and Azure

AspectAWSGCPAzure
Offer TypeContainer ProductTerraform K8s AppContainer Offer (K8s App)
PackagingContainer images + HelmHelm + Terraform moduleCNAB bundle
Commit DrawdownEDPMCPOMACC
Fee Structure3% contract / 1.5-3% private3% / 1.5% renewals~3% flat
ComplexityModerateLowestHighest

​
Troubleshooting

Verify the EKS node role has the ecr:GetDownloadUrlForLayer, ecr:BatchGetImage, and ecr:GetAuthorizationToken permissions. Ensure the ECR repository policy allows cross-account access if the customer’s EKS cluster is in a different AWS account.
Confirm the product code matches the listing ID in AMMP. Ensure the metering calls originate from within the customer’s AWS account using IRSA credentials.
Verify the customer’s EDP agreement covers AWS Marketplace purchases. Some older EDP agreements exclude marketplace spend — the customer should contact their AWS account team.

​
Next Steps

GCP Marketplace

Learn about the GCP Marketplace listing and GKE deployment.

Azure Marketplace

Learn about the Azure Marketplace listing and AKS deployment.