HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
neospe
autoops
Python2026–2026
neospe / autoops

autoops

Multi-region data and service mesh - operated by a Makefile.

2Distinct people
3Mentions
0Explicit recommenders
3GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Multi-region data and service mesh - operated by a Makefile.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day3 dated mentions

Observed mentions: 2026-06-24 11:45:17 UTC to 2026-07-17 13:29:36 UTC.

012026-06-24 00:00:00 UTC to 2026-06-25 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJun 242026-06-25 00:00:00 UTC to 2026-06-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-26 00:00:00 UTC to 2026-06-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-27 00:00:00 UTC to 2026-06-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-28 00:00:00 UTC to 2026-06-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-29 00:00:00 UTC to 2026-06-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-30 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-01 00:00:00 UTC to 2026-07-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-02 00:00:00 UTC to 2026-07-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-03 00:00:00 UTC to 2026-07-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-04 00:00:00 UTC to 2026-07-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-05 00:00:00 UTC to 2026-07-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 52026-07-06 00:00:00 UTC to 2026-07-07 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-07-07 00:00:00 UTC to 2026-07-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-08 00:00:00 UTC to 2026-07-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-09 00:00:00 UTC to 2026-07-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-10 00:00:00 UTC to 2026-07-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-11 00:00:00 UTC to 2026-07-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-12 00:00:00 UTC to 2026-07-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-13 00:00:00 UTC to 2026-07-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-14 00:00:00 UTC to 2026-07-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-15 00:00:00 UTC to 2026-07-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-16 00:00:00 UTC to 2026-07-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-17 00:00:00 UTC to 2026-07-18 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJul 17

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 242026-06-24 00:00:00 UTC2026-06-25 00:00:00 UTC110
Jun 252026-06-25 00:00:00 UTC2026-06-26 00:00:00 UTC000
Jun 262026-06-26 00:00:00 UTC2026-06-27 00:00:00 UTC000
Jun 272026-06-27 00:00:00 UTC2026-06-28 00:00:00 UTC000
Jun 282026-06-28 00:00:00 UTC2026-06-29 00:00:00 UTC000
Jun 292026-06-29 00:00:00 UTC2026-06-30 00:00:00 UTC000
Jun 302026-06-30 00:00:00 UTC2026-07-01 00:00:00 UTC000
Jul 12026-07-01 00:00:00 UTC2026-07-02 00:00:00 UTC000
Jul 22026-07-02 00:00:00 UTC2026-07-03 00:00:00 UTC000
Jul 32026-07-03 00:00:00 UTC2026-07-04 00:00:00 UTC000
Jul 42026-07-04 00:00:00 UTC2026-07-05 00:00:00 UTC000
Jul 52026-07-05 00:00:00 UTC2026-07-06 00:00:00 UTC000
Jul 62026-07-06 00:00:00 UTC2026-07-07 00:00:00 UTC110
Jul 72026-07-07 00:00:00 UTC2026-07-08 00:00:00 UTC000
Jul 82026-07-08 00:00:00 UTC2026-07-09 00:00:00 UTC000
Jul 92026-07-09 00:00:00 UTC2026-07-10 00:00:00 UTC000
Jul 102026-07-10 00:00:00 UTC2026-07-11 00:00:00 UTC000
Jul 112026-07-11 00:00:00 UTC2026-07-12 00:00:00 UTC000
Jul 122026-07-12 00:00:00 UTC2026-07-13 00:00:00 UTC000
Jul 132026-07-13 00:00:00 UTC2026-07-14 00:00:00 UTC000
Jul 142026-07-14 00:00:00 UTC2026-07-15 00:00:00 UTC000
Jul 152026-07-15 00:00:00 UTC2026-07-16 00:00:00 UTC000
Jul 162026-07-16 00:00:00 UTC2026-07-17 00:00:00 UTC000
Jul 172026-07-17 00:00:00 UTC2026-07-18 00:00:00 UTC110

What Hacker News says

3 sources
leschak·Jul 6, 2026Submission

Show HN: Autoops – Multi-region data and service mesh operated by a Makefile

Hi HN, Stefan here. autoops is an infrastructure automation framework I have been using at my previous company and is now opensourced. It has been the base layer running various products and projects, and also for quickly standing up client infra. It works with Debian-based systems (apt) and sets up a WireGuard mesh with peer discovery and built-in DNS (Wesher), a distributed S3-compatible object store (Garage), and a reverse proxy and load balancer (Traefik). It supports service autodiscovery (Traefik-kop) and can be horizontally scaled to up to 150-200 nodes. As a classical example of "roll your own k8s subset using scripting", it is not yet fully integrated and currently, you need 1) to define at least a PyInfra inventory, 2) depending on whether you run containered services, a Docker Compose file, and 3) for horizontal scaling with au
Read the rest
todiscovery, a Traefik config. The PyInfra scripts are put together in a Makefile, but that is pretty self explanatory. autoops doesn't trust supply chains, so you need to out-of-band put a couple of binaries in the general assets/ folder, and if you do containers, provide a path that contains directories named after each service and holding its Dockerfile and other build assets. Also, it's almost arm64 compatible (needs binaries for Docker and the crowdsec bouncer), can do NAT traversal (using my fork of Wesher), and container draining (using docker-rollout). Feedback is welcome.
4 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.