Alternatives
Products that do what Flux does
Server cost reducer & offline resilience engine for web app
- 1DA
Hey HN! I’ve written a bunch of WebSocket servers over the years to do simple things like state synchronization, WebRTC signaling, and notifying a client when a backend job was run. I realized that if I had a simple way to create a private, temporary, mini-redis that the client could talk to directly, it would save a lot of time. So we created DriftDB. In addition to the open source server that you can run yourself, we also provide https://jamsocket.live where you can use an instance we host on Cloudflare’s edge (~13ms round trip latency from my home in NY). You may have seen my…
2023 · driftdb.com
- 2RO
2017 · github.com
- 3
- 4SO
Nov 2025 · github.com
- 5
- 6SO
Aug 2026 · github.com
- 7
- 8
- 9RD
2019 · github.com
- 10
- 11DR
docker-compose is great for single node docker deployments, but it doesn't have a feature that would allow zero downtime deployments. It's not possible to deploy often if your app goes down every time, and using Kubernetes/Nomad/Swarm on a single node is an overkill. I created this Docker plugin to be a drop-in replacement for the restart command in usual docker-compose deployment scripts. It performs a simple rolling deployment of a single service.
2023 · github.com
- 12RL
Hi HN, I’ve wanted a simple solution to handle Wake-on-LAN sequences for my home and work labs to boot up servers in the right order. I was already dabbling in Rust and thought this would be an interesting project to dive deeper and see if it could work well for this kind of network tool. The result is rallyup. rallyup lets you set up server dependencies in a YAML file, so each service (e.g., firewalls, storage, VM hosts) comes online in the right order. It verifies each server’s status before moving to the next. Features: - Dependency-based WOL with VLAN support - Built-in health checks…
2024 · github.com
- 13GA
Hey HN, We've been experimenting with a real-time, version-controlled NoDB for Deno & React called GoatDB. The idea is to remove backend complexity while keeping apps fast, offline-resilient, and easy to self-host. Runs on the client – No backend required, incremental queries keep things efficient. Self-hosted & lightweight – Deploy a single executable, no server stack needed. Offline-first & resilient – Clients work independently & can restore state after server outages. Edge-native & fast – Real-time sync happens locally with minimal overhead. Why We Built It: We needed something that’s…
2025 · github.com
- 14VW
2020 · github.com
- 15IM
Hello! I got quite some feedback on a web server I'm building, so I'm rewriting the server to be faster and easier to use. I (and maybe some other contributors?) have optimized the web server performance, especially for static file serving and reverse proxying (the last use case I optimized for very recently). I also picked a different configuration format and specification, what I believe is easier to write. Automatic TLS is also enabled by default out of the box, you don't need to even enable it manually, like it was in the original server I was building. Yesterday, I released the first…
Oct 2025 · ferron.sh
- 16KA
A large part of our (Real Kinetic's) business is helping organizations implement platform engineering, but we've found the existing tooling to be lacking. For IaC, Terraform state becomes a pain because TF treats infrastructure as "one-shot" commands. The Kubernetes controller model provides a nicer approach to managing infrastructure, but the tooling here is also lacking. For configuration management, Helm just doesn't really scale with complexity, nor does Kustomize. For resource orchestration, Crossplane is a step in the right direction but still has challenges and limitations. As a…
2025 · koreo.dev
- 17SB
2018 · github.com
- 18
- 19SS
2017 · scripts.blockspring.com
- 20HA
2017 · hackend.xyz
- 21FA
2014 · github.com
- 22AS
Doors: Server-driven UI framework + runtime for building stateful, reactive web applications in Go. Some highlights: * Front-end framework capabilities in server-side Go. Reactive state primitives, dynamic routing, composable components. * No public API layer. No endpoint design needed, private temporal transport is handled under the hood. * Unified control flow. No context switch between back-end/front-end. * Integrated web stack. Bundle assets, build scripts, serve private files, automate CSP, and ship in one binary. How it works: Go server is UI runtime: web application runs on a…
Apr 2026 · github.com
- 23FA
Dec 2025 · github.com
- 24RS
2016 · redfin.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →