Quickstart

This page gets you from "wallet connected" to "first deploy live" in five steps. Each step has its own deeper guide if you need more detail; follow the links inline.

You'll need: a wallet (MetaMask, Rainbow, or any Reown-compatible wallet) or an email account, a GitHub account, and a static-site repository to deploy. If your repo isn't public, the GitHub App handles permissions. The dashboard works on desktop and phone browsers.

Stasho is in alpha. Read Alpha status & limits for quotas, known limitations, and how to report bugs.

1. Open the app

Open app.stasho.xyz. You should see two sign-in options: Connect wallet and Sign in with email.

2. Sign in

Pick the rail you prefer:

• Connect wallet — opens a wallet picker. Approve the connection, then sign the SIWE message your wallet shows. No transaction, no gas.
• Sign in with email — sends you a one-time code by email or routes you through Google. The app provisions an embedded wallet for you in the background.

You should now see your address (or email) in the breadcrumb at the top of the dashboard. See Connect & sign in for the details on what gets signed and why.

3. Connect GitHub

In the dashboard, click New project. The wizard's first step prompts you to install the GitHub App. Pick the org or personal account that owns the repo you want to deploy, and grant access to that repo (or all repos — your call).

You should now see a list of your repositories. See Import a repo for what to do if the list is empty or you want to manage access later.

4. Pick a repo and deploy

Select a repo. The app auto-detects the framework (Next.js static export, Vite, Vue, Nuxt static, or plain HTML) and proposes a build configuration. Confirm, then click Deploy.

The first deploy opens a pull request in your repo that adds the deploy workflow — the dashboard shows Setup pending until you merge it (the Merge & deploy button does it for you). After the merge, the workflow runs, builds, uploads the artifact, and pins it to IPFS.

You should see the deployment row in your dashboard cycle through queued → installing → building → uploading → pinning → live. See Your first deployment for what each phase means and how to read the GitHub Actions log when something fails.

5. View your site

When the deployment row reads live, click the gateway URL. Your site renders from IPFS through Aleph's gateway.

You're done. Subsequent pushes to the repo's main branch redeploy automatically.

What next

• Attach a custom domain so your site serves at your own host instead of the gateway URL.
• Manage deployments — redeploy, roll back instantly to a previous build, or abandon a stuck one.
• Set environment variables and adjust build settings without touching your repo.
• Your data on Aleph explains what's encrypted, what's public, and what the backend can and can't read.
• The Recover your data guide shows how to reconstruct your project history from public Aleph messages using only your wallet's private key — independent of our backend.
• The Aleph storage schema reference documents the wire format if you'd rather build your own tooling on top.