Run HASH as a hosted, local, or self-hosted instance
You can use HASH in three ways:
In most cases we recommend using the hosted version of HASH — there are no servers, containers, or API keys to manage — and you can move data and types between any of the three later.
With the hosted version of HASH, we operate the servers, perform upgrades, keep integrations current, and assure data security, leaving you free to simply manage your account.
We currently operate a waitlist and invite a small number of users each day, to keep the platform's growth manageable. To join, simply create an account and sign in. You can apply to jump the waitlist by providing more information about your intended use of HASH.
HASH can be run locally in the form of Docker containers on your own machine, orchestrated by a single Compose file.
You don't need to have Rust, Node or any other toolchain on the host machine as everything is built and runs inside containers. This abstracts away much of the complexity involved in running a production instance of HASH, which comprises various services: the frontend, API, hgres, various so-called "workers", plus underlying infrastructure (including Postgres, Redis, Kratos, Temporal, Vault, and MinIO).
Looking to develop HASH?
The steps documented here run HASH from container images, and are not the recommended approach for local development. Instead, see the repo README to run app services natively with support for hot-reloading.
Self-hosted HASH runs the same technology stack as Local HASH, albeit on cloud infrastructure you operate, or on-premises.
Self-hosting additionally requires setting up a raft of additional infrastructure.
Previous
Next
