Alternatives
Products that do what Ably AI Transport - a transport layer for agentic apps does
Hey HN, Staff Engineer at Ably here. Over the past few months I've been speaking to engineers building AI assistants, copilots, and agentic workflows (over 40 companies at this point), with particular focus on cloud-hosted agents. I expected the hard problems to be in model selection, prompt engineering, and orchestration. Instead, the same infrastructure challenges kept coming up: realtime sync between agents and end clients is surprisingly painful to get right. - Managing and scaling WebSocket or SSE connections between agents and clients - Buffering messages server-side and implementing…
- 1
- 2UA
Three months ago, we started developing an open source agent framework. We previously tried existing frameworks in our enterprise product but faced challenges in certain areas. Problems we experienced: * We risked our stateless architecture when we wanted to add an agented feature to our existing system. Current frameworks lack server-client architecture, requiring significant effort to maintain statelessness when adding an agent framework to your application. * Scaling problem - needed to write Docker configurations as existing frameworks lack official Docker support. Each agent in my…
2025 · github.com
- 3AA
We’ve published a set of open-source reference implementations on how to build production-grade Agentic AI applications on AWS. What’s in the repo: • Agentic RAG, memory, and planning workflows with LangGraph & CrewAI • Strands-based flows with observability using OTEL & Arize • Evaluation with LLM-as-judge and cost/performance regressions • Built with Bedrock, S3, Step Functions, and more GitHub: https://github.com/aws-samples/sample-agentic-frameworks-on-... Would love your thoughts — feedback, issues, and stars welcome!
2025 · github.com
- 4HG
Most AI applications are built for individuals but work happens in groups and humans want to collaborate with both agentic AI and other teammates in the same session. We created Hybrid Groups for that purpose. In Hybrid Groups, agents join group chats as virtual team members in Slack and GitHub. They participate in group conversations, proactively contribute when needed and perform actions on behalf of individual users, like managing your calendar for meeting suggestions or updating your todo list without sharing access to your private resources to the group. The project is open-source at…
2025 · youtube.com
- 5RA
Hi HN folks, I have been building AI agents for quite some time now. The shift has gone from LLM + Tools → LLM Workflows → Agent + Tools + Memory, and now we are finally seeing true agency emerge: agents as systems composed of tools, command-line access, fine-grained system capabilities, and memory. This way of building agents is powerful, and I believe it is here to stay. But the real question is: are the systems powering these agents ready for that future? I do not think so. Using Docker for a single agent is not going to scale well, because agents need to be lightweight and fast. LLMs…
Mar 2026 · github.com
- 6JA
Hey HN, I'm one of the creators of joinly.ai, an open-source solution that makes browser-based video conferences accessible to AI agents, allowing you to interact with them in real time. Think of it as a connector layer that brings the functionality of your AI agents to your meetings, allowing you to essentially build your own custom meeting assistant. We didn't want to build yet another Python framework for creating agents with its own syntactic sugar that you have to learn. That's why we opted for a different approach, utilizing an MCP server. Our MCP server provides essential meeting…
2025 · github.com
- 7AA
Hey HN! I am super excited (and slightly nervous) to introduce AgentServe! AgentServe is a framework to make hosting scalable AI agents as easy as possible. With 4 lines of code AS wraps your agent (any framework) in a FastAPI and connects it to a Task Queue (celery or redis). Why Should You Care? Standardized Communication Pattern: AgentServe proposes that all agents should communicate with each other and the outside world with “Tasks” that can be submitted in a sync or async way. This simple API wil enable Framework Agnostic: No favorites. OpenAI, LangChain, LlamaIndex, CrewAI are all…
2024 · github.com
- 8
Hi HN, my name is Maria, and I’m a co-founder of Maritime. We started Maritime at MIT to build infrastructure for companies that need to run thousands of isolated AI agents for their customers. Imagine you set up an agent like OpenClaw, or a personal assistant agent with a custom framework, and want to give a separate version of it to every customer/friend. Each customer needs their own agent running in an isolated microVM, with persistent state, secrets, triggers, and sleep/wake behavior. Building such scalable and secure infra will take you months and will cost hundreds of…
18d ago · maritime.sh
- 9AA
I’ve been experimenting with infrastructure for multi-agent systems. I built a small project called AgentLog. The core idea is very simple, topics are just append-only JSONL files. Agents publish events over HTTP and subscribe to streams using SSE. The system is intentionally single-node and minimal for now. Future ideas I’m exploring: - replayable agent workflows - tracing reasoning across agents - visualizing event timelines - distributed/federated agent logs Curious if others building agent systems have run into similar needs.
Mar 2026 · github.com
- 10PE
Hey HN — I’m Adil from Katanemo (with Salman, Shuguang, and Meiyu) We previously shared an early version of this project as ArchGW. Based on customer feedback, the scope expanded from “LLM routing and model access” into something broader: delivery infrastructure for agentic applications. We renamed it to Plano and reworked the architecture accordingly. The problem On-the-ground AI practitioners will tell you that calling an LLM is not the hard part. The really hard part is delivering agentic applications to production quickly and reliably, then iterating without rewriting system code every…
Jan 2026 · github.com
- 11IB
Hi HN, I’m the creator of Cordum. I’ve been working in DevOps and infrastructure for years (currently in the fintech/security space), and as I started playing with AI agents, I noticed a scary pattern. Most "safety" mechanisms rely on system prompts ("Please don't do X") or flimsy Python logic inside the agent itself. If we treat agents as autonomous employees, giving them root access and hoping they listen to instructions felt insane to me. I wanted a way to enforce hard constraints that the LLM cannot override, no matter how "jailbroken" it gets. So I built Cordum. It’s an open-source…
Jan 2026 · github.com
- 12FA
Founder here. I built NEO, an AI agent designed specifically for AI and ML engineering workflows, after repeatedly hitting the same wall with existing tools: they work for short, linear tasks, but fall apart once workflows become long-running, stateful, and feedback-driven. In real ML work, you don’t just generate code and move on. You explore data, train models, evaluate results, adjust assumptions, rerun experiments, compare metrics, generate artifacts, and iterate; often over hours or days. Most modern coding agents already go beyond single prompts. They can plan steps, write files, run…
Jan 2026 · marketplace.visualstudio.com
- 13CA
I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!
Sep 2025 · infrastructureas.ai
- 14
Sup HN! Dipanshu and Rushant here from Caspian. One is a functional programmer and the other has been deploying AI employees. Together we realized how agents have communication bottleneck. Given the coming agentic economy, we had a thought experiment on what can be the key infrastructure for agents as they get better. Our inspiration for solving for communications infra came from our own time spent just setting up comms while we were deploying open claw for companies plus we noticed about 15%+ of issues in Openclaw and Hermes were that of comms. So we abstracted the headache of reliable…
16d ago · github.com
- 15IM
Hey HN, I’m Chris, a solo dev in Melbourne AU. For the past month I've been spending my after work hours building AgentVisa. I'm both excited (and admittedly nervous) to be sharing it with you all today. I've been spending a lot of time thinking about the future of AI agents and the more I experimented, the more I realized I was building on a fragile foundation. How do we build trust into these systems? How do we know what our agents are doing, and who gave them permission? My long-term vision is to give developers an "Agent Atlas" - a clear map of their agentic workforce, showing where…
2025 · agentvisa.dev
- 16AR
Hi HN. I'm the founder of Phoenix Labs (ex TikTok, Applied AI) and we're open sourcing our internal tooling today which is like a toolchain / meta-harness for CLI agents useful for really scaling eng and creative work. We are a very small team who's building a very ambitious product so we had to find ways to squeeze every ounce of efficiency that we could get our hands on. Harness strengths of different models (Claude, GPTs) and CLI-harnesses (Claude Code, Codex), safe/robust browser integration to speed up UX/QA testing, teams cli to speed up security reviews and parallelize…
May 2026 · agents-cli.sh
- 17AC
Hi HN, I’m the author of agent-contracts, a Python library that explores a contract-based approach to structuring LangGraph agents. When building larger LangGraph-based systems, I kept running into the same issues: - node responsibilities becoming implicit - state dependencies spreading across the graph - routing logic getting harder to reason about - refactoring feeling increasingly risky agent-contracts is an attempt to make these boundaries explicit. Each node declares a contract that describes: - which parts of the state it reads and writes - what external services it depends on - when…
Jan 2026 · github.com
- 18IB
The main goal of this was to be able to not just run multiple Claude Code sessions at once, but actually manage them and keep track of what I was doing. Sometimes this is multiple attempts on the same task, sometimes I work several tasks at once. Really I was just sick of twiddling my thumbs waiting for the coding agent to finish, and I wanted it to be easy to work on/review/test another change while I waited.
2025 · github.com
- 19IA
Hello HN! My name is Max, and I’m a co-founder at Lynx (https://uselynx.ai). We’re building an AI-powered incident resolution platform to help engineers debug and resolve on-call issues faster. If you’ve ever been paged in the middle of the night and had to spend hours piecing together logs, metrics, and code, we’d love your feedback. * The Problem * On-call hasn’t kept pace with modern engineering. Even with great observability tools, diagnosing incidents is slow because: - Systems are increasingly complex. - Logs, dashboards, and documentation are scattered. - Context often…
2025
- 20MA
This weekend I built a multi-agent coding system which, quite unexpectedly, beat Claude Code on Stanford's Terminal Bench! The architecture is straightforward, consisting of an orchestrator agent that deploys explorer & coder subagents to complete complex terminal based tasks, utilising an intelligent context sharing mechanism along the way which makes it all work. The repo has a lot of technical details, and all the code and prompts for you to play around with if you'd like! I had a lot of fun making this, I hope you have fun reading the README, using it yourself, or even extending it! As…
2025 · github.com
- 21HW
We have been exploring ways to coordinate AI agents and services cleanly, observably, and without turning everything into YAML spaghetti. We came across this repo Happen, how good will it be cause we have We’ve tried the usual stuff: LangChain (too bloated, too magic) Autogen (chat loop hell) CrewAI (fun, but brittle when workflows grow) https://github.com/RobAntunes/Happen/tree/main/examples
2025 · github.com
- 22IV
Coding agent management is all the rage right now, and many tools are being created to fill the gap. As a power user for all tools I've used since I've started my software engineering career, I've always taken the time to test multiple tools thoroughly before deciding on one, and an agentic manager was no different. I've tested many tools, but ultimately landed on Agent of Empires (AoE for short). Why ? Because it's fast, the development is active and it's feature complete, and easy to contribute to. So I did (contribute). In my day to day workflow for my job, I need the ability to start…
May 2026 · github.com
- 23SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 24GT
Hi folks, I built this guide after watching AI agent prototypes repeatedly fail in production. It demonstrates transforming a monolithic marketplace assistant into a resilient multi-agent system using orra, an open-source platform I also built for production-ready multi-agent applications. The patterns shown are valuable *even if you're building your own orchestration layer*. Each stage builds on the previous one, showing the evolution from fragile prototype to resilient system. What makes this guide valuable: * Architectural transformation with working code examples - split monolithic…
2025 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →