AW3 - Multi-Cloud Hosting Platform

    Ship to every cloud.
    From one control plane.

    Connect Vercel, AWS, Railway, Cloudflare and thirteen more once. Roll out with canary or blue/green, split traffic by weight or region, and fail over on its own — from the dashboard, a git push or one API call.

    500 free credits a month · No card needed · Dashboard, git push or REST API

    Connect each provider once. Deploy to any of them.

    • Verceledge
    • AWSecs · lambda
    • Cloudflareworkers
    • Railwayfull stack
    • Google Cloudcloud run
    • Azurefunctions
    • Fly.iomachines
    • Renderservices
    • DigitalOceanapp platform
    • Netlifyfrontend
    • Supabasebackend
    • Kubernetesany cluster
    • Hetznerbare metal
    • Linodevms
    • CoreWeavegpu
    • RunPodgpu
    • Modalgpu
    Multi-cloud control plane

    Not another cloud.
    The layer above all of them.

    Your providers stay your providers. AW3 sits on top: one place to deploy, route, watch and pay for everything they run.

    01

    One deploy, any provider

    Point a service at Vercel today and AWS tomorrow without rewriting a pipeline. AW3 holds the credentials, builds once and ships to whichever targets you choose.

    17 providers · git push or API

    02

    Rollouts that undo themselves

    Standard, blue/green or a canary that walks 1 → 5 → 25 → 100%. If the error rate climbs, AW3 rolls traffic back to the last good version on its own.

    canary · blue/green · instant rollback

    03

    Traffic that routes itself

    Weight traffic across providers, pin users to the nearest region, and fail over to a standby when a health check misses. Checks run every 60 seconds.

    weighted · geo · failover

    04

    Spend you can see

    Daily cost sync from every connected provider, broken down by service, environment and region, with budget caps that block a deploy before it blows the month.

    cost sync · budget policies · AI recommendations

    How it works

    Connect. Deploy.
    Let it route.

    Three steps from a repository to traffic spread across providers, with a rollback waiting if you need it.

    Vercel
    AWS
    Cloudflare
    Railway
    01

    Connect

    Add your provider accounts. Credentials are encrypted with AES-256-GCM and only decrypted in memory at deploy time.

    • 17 providers
    • Scoped per environment
    • GitHub push-to-deploy
    POST /deployments strategy=canary
    ✓ build a41c9e2 · 38s
    ✓ secrets diffed · 0 changes
    ✓ policy budget-cap passed
    → canary live on cloudflare · 5%
    02

    Deploy

    Ship from the dashboard, a git push or one API call. Policies for budget, region and approvals run before anything goes live.

    • Canary, blue/green, standard
    • Secret diff before deploy
    • Live log streaming
    1%
    5%
    10%
    25%
    50%
    100%
    failover → railwayarmed
    03

    Let it route

    AW3 ramps traffic, watches health and latency, and moves users to a healthy target when something breaks.

    • Weighted and geo routing
    • 60-second health checks
    • Automatic rollback
    17

    Cloud and GPU providers behind one API

    4

    Deploy strategies, including canary and blue/green

    6

    Routing modes, from weighted to geo to failover

    60s

    Between health checks on every target

    For developers

    Everything the dashboard does,
    one request away.

    AW3 is API-first. The same endpoints that power the dashboard are yours, so deploys, traffic shifts and rollbacks fit into whatever pipeline you already run.

    • Scoped API tokens per org
    • Outbound webhooks for deploy, health, cost and policy events
    • GitHub push-to-deploy with HMAC-verified webhooks
    • Full audit log with CSV export
    curl -X POST https://app.aw3.host/api/deployments \
    -H "Authorization: Bearer $AW3_TOKEN" \
    -H "Content-Type: application/json" \
    -d '{
    "serviceId": "svc_api",
    "strategy": "canary",
    "canaryPercent": 5
    }'
    Why AW3

    One control plane.
    Not seventeen consoles.

    Without AW3
    With AW3
    A pipeline, a dashboard and a set of credentials per provider
    One deploy API in front of all 17 providers
    Moving a service off a provider means rewriting its deploy
    Change the target, keep the pipeline
    Canary and blue/green built by hand, if at all
    Canary, blue/green and rollback as a setting
    Failover is a runbook someone follows at 3am
    Health checks every 60s and an automatic standby
    Cost lives in five billing pages, read once a month
    Daily cost sync with budget caps enforced at deploy
    Secrets copied between consoles by hand
    Encrypted, environment-scoped secrets, diffed before every deploy
    Pricing

    Start free.
    Pay for what you ship.

    Credits cover deploys, bandwidth and compute on every provider you connect. No hidden fees.

    MonthlyAnnual (Save 20%)

    Starter

    Perfect for side projects and learning

    Freeforever
    500 credits included
    3 connected platforms
    5 projects
    Community support
    Basic analytics
    7-day log retention
    Most Popular

    Pro

    For professional developers and small teams

    $29/month
    10,000 credits/month
    Unused credits roll over
    Unlimited platforms
    Unlimited projects
    Priority support
    Advanced analytics
    30-day log retention
    Custom domains
    Team collaboration (5 seats)

    Enterprise

    For organizations with advanced needs

    Custompricing
    Unlimited credits
    Everything in Pro
    Unlimited team seats
    Contractual uptime SLA
    Dedicated support
    90-day log retention
    SSO / SAML
    Custom contracts

    Need More Credits?

    Purchase credit packs anytime. They never expire and work with any plan.

    Enterprise

    Need a custom solution?

    Get a tailored plan for your organization with custom limits, dedicated support, SLAs, and advanced security features.

    SSO
    SAML & SCIM
    24/7
    Support
    Custom
    Contracts
    SOC 2
    Audit in progress

    Frequently Asked Questions

    What are credits used for?

    Credits are consumed based on your hosting usage including deployments, bandwidth, and compute time. Different actions consume different amounts of credits.

    Do unused credits expire?

    On the Pro plan, unused credits roll over to the next month. Free tier credits reset monthly. Credit pack purchases never expire.

    Can I buy additional credits?

    Yes! You can purchase credit packs at any time to top up your account, regardless of your plan.

    What happens if I run out of credits?

    We'll notify you when you're running low. You can purchase additional credits or upgrade your plan to continue without interruption.

    Blog

    Field notes on
    running multi-cloud.

    Engineering write-ups, guides and product news, with sources for every number.

    Public beta

    Your next deploy
    goes everywhere.

    Connect a provider, point a service at it, and ship. Add the second provider when you're ready.

    No card needed · Free tier · Pay as you go after that