wabiDocs
Connect wallet

Overview

wabi runs your web services, workers and Postgres databases, each in its own microVM, and serves your static sites. Your variables are sealed in your browser and open only inside that microVM. You sign in with a Solana wallet and pay ahead in USDC.

  1. Your appAn image, a repository or a folder.
  2. VariablesSealed in your browser, opened in your microVM.
  3. ComputeA microVM for each service you run.
  4. NetworkOne private network for your services alone.
  5. DomainsAn address on projectwabi.app, and your own.
  6. AccountYour Solana wallet.
  7. PaymentUSDC on Solana, paid ahead.
The layers under your app, from your app at the top to payment at the base.

What you can run

  • Web services answer HTTP at their own address, from a public image or a GitHub repository. See Services, Deploy an image and Deploy from GitHub.
  • Workers run the same way with no public address, for queue consumers, bots and other background processes. See Services.
  • Postgres databases run in their own microVM, with credentials made in your browser and an encrypted backup every day. See Postgres.
  • Static sites serve a folder you upload. Without a plan, three are free. See Static sites.

From source to a live URL

  1. You point a service at a source: a public image, a branch of a GitHub repository, or a folder you upload.
  2. A repository builds in a microVM of its own, with its Dockerfile or with Cloud Native Buildpacks.
  3. wabi pins the image by digest and starts it in a new Kata microVM. The first process inside checks your wallet-signed variables manifest, opens the values in the VM's memory and starts your app.
  4. Once the health check passes, the new deployment takes traffic at https://<label>.projectwabi.app and the previous one stops.

A deployment that fails never touches what is live: the previous one keeps serving. Every deployment of a web service or worker is a snapshot you can roll back to without a rebuild.

Static sites run no code of yours. Each upload is scanned, then served as files from the same kind of address.

What stays private

Variables are sealed in your browser to your tenant's key, signed by your wallet, and opened only inside your service's microVM, so wabi stores and forwards ciphertext it cannot read (Sealed variables). A service can also sign Solana transactions with no private key in its environment, from an account nothing on chain ties to your wallet (Keyless backends).

How you pay

Your Solana wallet is your account: signing in is a signed message, never a transaction (Wallet sign-in). Plans are paid ahead in USDC for one, three or twelve months (Plans and payment). Staking WABI takes up to 30% off each payment and adds resources on top of your plan (Staking).