A distributed workflow engine written in Go

Hi HN, I'm Mohammed, a technical founder who loves shipping and giving back to the community. I'm open-sourcing the full-stack engine that powers my B2B product, apflow.co. What it is: A production B2B starter with a Go backend and Next.js frontend. Both are fully Dockerized with separate containers. No Vercel. No Supabase. Deploy the whole thing on a $6 VPS, or split frontend and backend across different providers. You own the infrastructure. The problem I was solving: Every SaaS starter I evaluated had the same issue: they locked me into someone else's platform. Vercel for hosting.…

I think graph is a wrong abstraction for building AI agents. Just look at how incredibly hard it is to make routing using LangGraph - conditional edges are a mess. I built Laminar Flow to solve a common frustration with traditional workflow engines - the rigid need to predefine all node connections. Instead of static DAGs, Flow uses a dynamic task queue system that lets workflows evolve at runtime. Flow is built on 3 core principles: * Concurrent Execution - Tasks run in parallel automatically * Dynamic Scheduling - Tasks can schedule new tasks at runtime * Smart Dependencies - Tasks can…

Hi HN! During the last few years, I worked on a few applications built with Go, running on AWS Lambda. As I got to know the platform better, I started to find Go & Lambda to be a really productive combination. The applications were fast, and they ended up being much cheaper to run than what my team & I had built before. It’s probably not the best platform for _every_ application, but I was surprised at how much of our workload worked well on it. As we brought new engineers on to our team and helped them get up to speed with the stack, I found that we were covering a lot of the same topics…