Aspabase

DEMO
No Instance

66% faster than RDS. 50% cheaper.

Fully managed MySQL on local NVMe storage. No network-attached EBS. No provisioned IOPS bills. Just raw NVMe performance.

Live Benchmark

Aspabase (NVMe) vs RDS (gp3) — sysbench OLTP

Read/Write · 10 tables × 1,000K rows · 5GB buffer pool · 32 threads · 180s

Why Aspabase

66% Faster
Local NVMe + HomeStore. No EBS, no network hops.
Scale Out in 1s
Add read capacity instantly when traffic spikes.
Scale to Zero
Pay nothing when there's no traffic.
Drop-in Replacement
Same MySQL protocol. Same connection string.
No Vendor Lock-in
Not even to Aspabase. Your data, your cloud.
Branches
Instant database branches with redaction. Perfect for dev/test.
Multi-Cloud
Deploy on AWS, GCP, or Azure. Your choice.
BYOC
Bring Your Own Cloud. Run in your own account.
BYOL
Bring Your Own License. Use your existing contracts.

Architecture

How Aspabase delivers NVMe performance with cloud durability.

Your Application
Standard MySQL connection
Proxy Layer
Connection routing, read/write splitting, scale out
MySQL (primary)
Unmodified, 100% compatible
Aspabase Agent
HomeStore + ublk
NVMe
MySQL (replica 1)
Unmodified, 100% compatible
Aspabase Agent
HomeStore + ublk
NVMe
MySQL (replica 2)
Unmodified, 100% compatible
Aspabase Agent
HomeStore + ublk
NVMe
S3
Object store — async write from primary, replicas read from S3
1 node — scaled in 0sreplicas created from S3 in ~1s

Proxy Layer

Routes connections across MySQL nodes. Handles read/write splitting for scale-out. Enables instant failover and zero-downtime scaling.

MySQL + Aspabase Agent

Each node runs unmodified MySQL with the Aspabase Agent alongside. The agent intercepts block I/O via HomeStore and ublk, bypassing the kernel for direct NVMe access. HomeStore has been powering exabytes of storage at eBay for over 5 years.

Local NVMe

Hot data lives on local NVMe drives (1.5M+ IOPS, sub-ms latency). No network-attached EBS. No provisioned IOPS bills.

S3 — Object Store

The agent on the primary async writes to S3. When scaling out, new replicas read from S3 and boot in ~1 second — no data copying from the primary, no replication lag.

Live Monitoring

TPS / QPS

Launch instance to view live metrics

P95 Latency

Launch instance to view live metrics

Disk IOPS

Launch instance to view live metrics

Aspabase Disk Latency (ms)

Launch instance to view live metrics

Cost Comparison

Actual AWS billing for equivalent 16-vCPU instances with 16K provisioned IOPS.

Aspabase (NVMe)RDS gp3RDS io1
Instance$1,044/mo$1,254/mo$1,254/mo
Storageincluded$58/mo$50/mo
Provisioned IOPSN/A$80/mo$1,600/mo
Total$1,044/mo$1,392/mo$2,904/mo
Cost / TPS$0.60$1.33$2.80

NVMe: im4gn.4xlarge. RDS: db.r6g.4xlarge. Both 16 vCPU. Storage: 500 GB gp3/io1 with 16K provisioned IOPS.

How Aspabase Compares

Side-by-side with major managed MySQL providers.

FeatureAspabaseRDS MySQLAurora MySQLGCP Cloud SQLAzure MySQL
StorageLocal NVMeEBS (gp3/io1)Distributed (proprietary)Persistent DiskManaged Disk
IOPSIncluded (1.5M+)Provisioned ($$$)Auto-scalesProvisioned ($$$)Provisioned ($$$)
Performance vs RDS+66%Baseline~3-5x (claimed)~4x (Enterprise+)~1x
Scale to ZeroYesNoServerless v2NoNo
Scale Out~1sMinutesMinutesMinutesMinutes
Branching (COW)Yes (instant)NoNoFast clone (same zone)No
Cost (16vCPU, 16K IOPS)~$1,044/mo~$1,392/mo~$1,800/mo~$1,500/mo~$1,400/mo