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”.

We run the following services internally to support the OpenWrt project:

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 servers	DigitalOcean	Managed DNS service	DigitalOcean	DigitalOcean admins
DNS registry	Gandi	Managed by SFC	Gandi
CDN	Fastly	Content delivery network		aparcar
Sysupgrade server storage	Cloudflare R2 + workers + D1 (SQL)	Sysupgrade server image cache management	Cloudflare	aparcar, ansuel
Github formal check bot	Cloudflare workers		Cloudflare	aparcar, ansuel
Github CI cache	Cloudflare R2	Object storage for ccache	Cloudflare	aparcar, ansuel

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
	DigitalOcean droplets	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 detect updates to the source and kick off the build process for each supported device.

• 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).

There are several buildbot instances, phase1 to build images, and phase2 to build packages.

Many third-parties are providing mirrors of the main OpenWrt download archive.

See mirrors

• 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.

See the Donations page.