<p align="center"> <a href="https://elk.zone" target="_blank" rel="noopener noreferrer"> <img width="160" height="160" src="./public/logo.svg" alt="Elk logo"> </a> </p> <h1 align="center"/>Elk <sup><em>alpha</em></sup></h1> <p align="center"> A nimble Mastodon web client </p> <br/> <p align="center"> <a href="https://chat.elk.zone"><img src="https://img.shields.io/badge/chat-discord-blue?style=flat&logo=discord" alt="discord chat"></a> <a href="https://pr.new/elk-zone/elk"><img src="https://developer.stackblitz.com/img/start_pr_dark_small.svg" alt="Start new PR in StackBlitz Codeflow"></a> <a href="https://volta.net/elk-zone/elk?utm_source=elk_readme"><img src="https://user-images.githubusercontent.com/904724/209143798-32345f6c-3cf8-4e06-9659-f4ace4a6acde.svg" alt="Open board on Volta"></a> </p> <br/> <p align="center"> <a href="https://elk.zone/" target="_blank" rel="noopener noreferrer" > <img src="./public/elk-og.png" alt="Elk screenshots" width="600" height="auto"> </a> </p>

⚠️ Elk is in Alpha

It is already quite usable, but it isn't ready for wide adoption yet. We recommend you use it if you would like to help us build it. We appreciate your feedback and contributions. Check out the Open Issues and jump in the action. Join the Elk discord server to chat with us and learn more about the project.


Official Deployment

The Elk team maintains a deployment at:

Self-Host Docker Deployment

In order to host Elk yourself you can use the provided Dockerfile to build a container with elk. Be aware, that Elk only loads properly if the connection is done via SSL/TLS. The Docker container itself does not provide any SSL/TLS handling. You'll have to add this bit yourself. One could put Elk behind popular reverse proxies with SSL Handling like Traefik, NGINX etc.

  1. checkout source git clone https://github.com/elk-zone/elk.git
  2. got into new source dir: cd elk
  3. build Docker image: docker build .
  4. create local storage directory for settings: mkdir elk-storage
  5. adjust permissions of storage dir: sudo chown 911:911 ./elk-storage
  6. start container: docker-compose up -d

[!NOTE] The provided Dockerfile creates a container which will eventually run Elk as non-root user and create a persistent named Docker volume upon first start (if that volume does not yet exist). This volume is always created with root permission. Failing to change the permissions of /elk/data inside this volume to UID:GID 911 (as specified for Elk in the Dockerfile) will prevent Elk from storing it's config for user accounts. You either have to fix the permission in the created named volume, or mount a directory with the correct permission to /elk/data into the container.


These are known deployments using Elk as an alternative Web client for Mastodon servers or as a base for other projects in the fediverse:

Note: Community deployments are NOT maintained by the Elk team. It may not be synced with Elk's source code. Please do your own research about the host servers before using them.

πŸ’– Sponsors

We are grateful for the generous sponsorship and help of:

<a href="https://nuxtlabs.com/" target="_blank" rel="noopener noreferrer" > <img src="./images/nuxtlabs.svg" alt="NuxtLabs" height="85"> </a> <br><br> <a href="https://stackblitz.com/" target="_blank" rel="noopener noreferrer" > <img src="./images/stackblitz.svg" alt="StackBlitz" height="85"> </a> <br><br>

And all the companies and individuals sponsoring Elk Team and the members. If you're enjoying the app, consider sponsoring us:

Or you can sponsor our core team members individually:

We would also appreciate sponsoring other contributors to the Elk project. If someone helps you solve an issue or implement a feature you wanted, supporting them would help make this project and OS more sustainable.

πŸ“ Roadmap

Open board on Volta

πŸ§‘β€πŸ’» Contributing

We're really excited that you're interested in contributing to Elk! Before submitting your contribution, please read through the following guide.


You can use StackBlitz Codeflow to fix bugs or implement features. You'll also see a Codeflow button on PRs to review them without a local setup. Once the elk repo has been cloned in Codeflow, the dev server will start automatically and print the URL to open the App. You should receive a prompt in the bottom-right suggesting to open it in the Editor or in another Tab. To learn more, check out the Codeflow docs.

Open in Codeflow

Local Setup

Clone the repository and run on the root folder:

pnpm i
pnpm run dev

Warning: you will need corepack enabled, check out the Elk Contributing Guide for a detailed guide on how to set up the project locally.

We recommend installing ni, that will use the right package manager in each of your projects. If ni is installed, you can instead run:

nr dev


Elk uses Vitest. You can run the test suite with:

nr test

πŸ“² PWA

You can consult the PWA documentation to learn more about the PWA capabilities on Elk, how to install Elk PWA in your desktop or mobile device and some hints about PWA stuff on Elk.

πŸ¦„ Stack

πŸ‘¨β€πŸ’» Contributors

<a href="https://github.com/elk-zone/elk/graphs/contributors"> <img src="https://contrib.rocks/image?repo=elk-zone/elk" /> </a>

πŸ“„ License

MIT Β© 2022-PRESENT Elk contributors