OpenWrt project infrastructure
The OpenWrt project relies on the considerable efforts of its volunteer developers, the core documentation team, the forum moderators, and the host of people who're actively using and testing the products. The OpenWrt team has also provisioned many physical and virtual servers that “make the OpenWrt project go”.
Services
Internally-managed services
We run the following services internally to support the OpenWrt project:
| Service | Technology | Description | Server | Statistics | Admin(s) |
|---|---|---|---|---|---|
| Website and documentation | Dokuwiki | Primary OpenWrt website and documentation/wiki | DigitalOcean droplet | awstats | bobafetthotmail, jow, thess, zorun |
| Forum | Discourse | Provides a place for people to ask and answer questions about using OpenWrt, developing it, and other topics | DigitalOcean droplet | hauke, jow, thess, psherman | |
| Git server | gitweb | Primary OpenWrt source code repositories | DigitalOcean droplet | gitstats | jow, thess |
| exim/dovecot | Handles incoming emails to @openwrt.org domain and forum mail | DigitalOcean droplet | jow, thess, stintel | ||
| Buildbot master | Buildbot | Coordinates builders | Hetzner | jow, ynezz | |
| Downloads | Hosts all current and released images, SDK, Imagebuilder | Hetzner | awstats | jow, thess | |
| Downloads archive | Hosts old OpenWrt images and releases | private co-lo | wigyori | ||
| Old wiki archive | Old OpenWrt wiki with legacy / non-migrated content | private co-lo | wigyori | ||
| Sources archive | Hosts a copy of sources of all software used in OpenWrt | Hetzner | jow, thess | ||
| Freescout | Freescout | Facilitates handling of shared mailboxes (testing) | DigitalOcean droplet | stintel | |
| Mailing lists | Mailman | Main medium of communication for developers and admin | infradead | dwmw2 | |
| Firmware selector | Search and download OpenWrt firmware for your device | ||||
| Sysupgrade server | Online ImageBuilder and upgrade server | stats | aparcar |
Externally-managed services
We also rely on the following services that are run by external entities:
| Service | Technology | Description | Host | Admin(s) |
|---|---|---|---|---|
| Patch tracking | Patchwork | Used to track patches sent to the openwrt-devel mailing list | Ozlab | ? |
| Bug tracker and pull requests | Github | The place where bugs and feature requests are tracked | Github | jow, thess |
| DNS | DigitalOcean | Managed DNS service | DigitalOcean | DigitalOcean admins |
| CDN | Fastly | Content delivery network |  | aparcar |
Hosting infrastructure and costs
Servers
All services that are managed internally are run on servers devoted to the OpenWrt project, except for mailing lists which run on Infradead servers.
| Host | Servers | Services | Admin(s) | Expected cost | Actual cost | Comment |
|---|---|---|---|---|---|---|
 | RS 8000 G9.5 a1 12M + 6TB storage | Downloads | aparcar | 100€ / month | Free | Open source project support |
 | 7 droplets (prod) | wiki, forum, git, mails... | jow, ynezz, stintel, lynxis, blogic, aparcar, thess, ldir | 344.00 $ / month | Free | Open source project support |
| Hetzner | ax41-nvme | Buildbot master | OpenWrt sysadmins | 35 € / month | 35 € / month | Paid privately |
| Hetzner | sb59 | Archive | blogic | 49.50 € / month | 49.50 € / month | Paid privately |
| Hetzner | ax61-nvme + 2x 1.92 TB SSD | Downloads | jow | 158.27 € / month | 158.27 € / month | Paid privately |
Buildbot workers
Buildbot workers detect updates to the source and kick off the build process for each supported device.
| Host | Name | Server spec | Nb servers | Admin(s) | Cost | Comment |
|---|---|---|---|---|---|---|
| Hetzner | subnetica-dock-* | AMD EPYC 7502P 32c/64t, 1x SSD SATA 1,92 TB Datacenter, 128GB RAM | 1 | OpenWrt sysadmins | 80€ / month | Provided by Subnetica, ,FSN1 datacenter |
| OVH | robimarko-dock-01 | AMD Epyc 7351p, 16c/32t, 128GB RAM, 2x500GB NVME | 1 | robimarko, ynezz | 43$ / month | Paid privately |
| OSUOSL | osuosl-vm-* | OpenStack VM (12 cores, 32 GB RAM, 320 GB disk) | 4 | zorun, ynezz, jow | Free | Open source project support |
| OSUOSL | osuosl-dock-* | 12C, 24T, 64 GB RAM (2x Xeon X5680 3.33 GHz) | 2 | OpenWrt sysadmins | Free | Open source project support |
| VZFFNRMO | vzffnrmo-dock-* | AMD EPYC 7451, 100 GB RAM, 200 GB disk | 4 | OpenWrt sysadmins | ? | Provided by the Freifunk Karlsruhe Project / VZFFNRMO e.V. |
| FFFFM | ffffm-dock-* | 28C, 56T, 448GB RAM, 1.8TB (2x Xeon E5-2680v4 2.4GHz) | 1 | OpenWrt sysadmins | Free | Provided by Freifunk Frankfurt am Main e.V. |
| FFB | ffb-dock-* | 12 cores E5-2630 + 64G RAM + 100G HDD | 1 | OpenWrt sysadmins | Free | Provided by Freifunk Berlin |
Worker hardware requirements
- CPU: a good worker needs 4-8 CPU cores for phase1/images, and 8-16 CPU cores for phase2/packages. Larger machines are split into several workers using Docker.
- Memory: each worker needs a minimum of 1 GB of RAM for each CPU hardware thread, 2 GB / thread is preferred. For example, a 16 cores / 32 threads machine needs between 32 GB and 64 GB of RAM in total.
- Disk: each worker needs either 50 GB of disk space (for phase1/images) or 150 GB of disk space (for phase2/packages).
Other costs
| What | Provider | Admin(s) | Expected cost | Actual cost | Comment |
|---|---|---|---|---|---|
| Domain names | Tucows | SPI Hostmaster / jow | 20-40 € / year | Free | Held by Tucows on behalf of SPI |
Buildbot build matrix
There are several buildbot instances, phase1 to build images, and phase2 to build packages.
| Version | Phase 1 - Images | Phase 2 - Packages | Fail logs | Image downloads |
|---|---|---|---|---|
| main | Phase 1 - Images | Phase 2 - Packages | Fail logs | images |
| 25.12 | 25.12 Images | 25.12 Packages | Fail logs | images |
| 24.10 | 24.10 Images | 24.10 Packages | Fail logs | images |
| 23.05 | 23.05 Images | 23.05 Packages | Fail logs | images |
Mirrors and archive
Many third-parties are providing mirrors of the main OpenWrt download archive.
See mirrors
Finances
- Each of the Hetzner servers costs about 50 Euros per month, for a total of 150 Euros/month.
- There is a small annual charge (20-40 Euros) for registering the domain names, etc.
- As of late 2016, two core team members are personally covering the costs of the Hetzner servers while another core team member picks up the other fees. So far, no one has stepped up to fund the new servers that will be required in the coming months.
- Other private parties generously donate their time & compute cycles, you know who you are and we thank you.
Donations
See the Donations page.