Building AetherGrid: an AI orchestrator that survives real worker failures
I've spent years chasing race conditions in production systems, revenue systems handling real money, Kafka worker queues, and now reviewing LLM-generated backend code for a living. The pattern is always the same: code works fine until something fails mid-execution, then two processes think they own the same job.
AetherGrid is my answer to that. Job execution ownership runs on time-bound leases that renew continuously for the job's whole runtime, not a boolean flag that lies to you the moment a worker crashes or a heartbeat drops. Real subprocess execution with enforced timeouts, reconciliation that reclaims abandoned work, 280 tests behind it, including one that genuinely kills a process that ignores SIGTERM.
Live now on Product Hunt, launching August 21st. Would love feedback from anyone who's dealt with execution ownership or lease-based systems in their own infra, and happy to answer anything about the architecture.

p/offiai
p/lasso-11
p/runevr
p/google-cloud-platform
p/producthunt
p/many-displays
p/reso
p/kodlo
p/ai-context-flow
p/htmldrag
p/dex-by-exmergo
p/dino-kids
p/jot-2-0
p/beamfy
p/refs
p/nexupira
p/duckfightclub
p/supabase
p/jev
p/nudgeforme
Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.