Skip to content

Web3 Hosting on Aleph.im

Overview

Aleph.im offers web3 hosting services via the Twentysix Cloud Console, allowing you to deploy any kind of Dapps in few simple steps. Your websites are stored on IPFS and are fully-managed by the Aleph network.

Aleph.im being GDPR-compliant, if you decide to delete your website, or some older versions of it (previous deployments), or if you stop holding the required amount of tokens to keep it online, your website will be automatically garbage collected after a grace period by our network.

ℹ️ IPFS being a public P2P network, your files may still be available over the network if external nodes pinned them.

Getting started

Prepare

You need to provide a root folder containing your static website's files.

Simple Static Website

The minimal requirement is that your folder must contain an index.html file. This file will always be the entrypoint of your website.

static-folder
├── index.html [required]
├── style.css
├── script.js
├── assets
:   └── ...

Framework-based Website

We are listing the officially supported frameworks on TwentySix's website creation page, but you can actually use any framework (and package manager, such as npm, pnpm, yarn, bun...) to create your website.

ℹ️ Keep in mine that your website, being a decentralized frontend, must only contain client-side components, as well as the dependencies used by it. For backend support, check out the section below.

Build

When your project is ready, you can build and generate your static folder. Example using npm:

npm install
npm run build

ℹ️ The name of the output folder depends on the framework used, it's usually out or dist.

Deploy

When your static folder is ready, you can deploy your website using the Twentysix Cloud Console.

Deploy your website

History and Updates

You can update your website or access/redeploy previous versions easily through your Website Management Dashboard.

Update website and access history

Access Your Dapp

Aleph Gateway Service

When your website is live on Aleph network, we provide you a gateway url to easily access it:

https://{ipfs-cid-v1}.ipfs.aleph.sh

You can also access it in a similar fashion using alternative gateways, since your website is hosted on IPFS. Find alternative gateways here.

Custom Domains

At deployment time, or later, you can link a custom domain to your website using:

ENS Domains

Since your website is hosted on IPFS, it is compatible with ENS domains.
To resolve it:

  • Access your domain page on ens.domains
  • Records ➜ Edit Records ➜ Other
  • Setup Content Hash to: ipfs://{ipfs-cid-v1}

ENS record

Your website will then be accessible via:

https://{ens-domain}.eth.limo
or
https://{ens-domain}.eth.link

Advanced Features

Handle Redirections on IPFS

By default, IPFS can't handle any fallback redirections, so we provide a 404 fallback for all routes that are not found.

If you want to add more specific redirections, you must create a _redirects file into your dapp:

  • Simple website: It should be located in the root folder.
  • Framework-based website: it should be located in the public folder. At build time, it will be moved at the root.

Check out the IPFS documentation below for more details.

Useful Links

Backend Support

In order to add a backend to your website and to make it a complete fullstack dapp, there are currently 2 different approchs you can implement:

ℹ️ You should setup your backend in advance, in order to integrate the needed endpoint urls inside your website after.

Auto-Deployment on Push

Coming soon.

Troubleshooting

aleph-sdk-ts

When using the Typescript SDK, some frameworks can require a specific setup.

Found an issue?

If the documentation didn't help, you can report an issue.