Alternatives
Products that do what I put an AI agent on a $7/month VPS with IRC as its transport layer does
The stack: two agents on separate boxes. The public one (nullclaw) is a 678 KB Zig binary using ~1 MB RAM, connected to an Ergo IRC server. Visitors talk to it via a gamja web client embedded in my site. The private one (ironclaw) handles email and scheduling, reachable only over Tailscale via Google's A2A protocol. Tiered inference: Haiku 4.5 for conversation (sub-second, cheap), Sonnet 4.6 for tool use (only when needed). Hard cap at $2/day. A2A passthrough: the private-side agent borrows the gateway's own inference pipeline, so there's one API key and one billing relationship…
- 1
- 2NC
I’ve been running Clawdbot for the last couple weeks and have genuinely found it useful but running it scares the crap out of me. OpenClaw has 52+ modules and runs agents with near-unlimited permissions in a single Node process. NanoClaw is ~500 lines of core code, agents run in actual Apple containers with filesystem isolation. Each chat gets its own sandboxed context. This is not a swiss army knife. It’s built to match my exact needs. Fork it and make it yours.
Feb 2026 · github.com
- 3
- 4
- 5
- 6
- 7
- 8AA
I built Axe because I got tired of every AI tool trying to be a chatbot. Most frameworks want a long-lived session with a massive context window doing everything at once. That's expensive, slow, and fragile. Good software is small, focused, and composable... AI agents should be too. Axe treats LLM agents like Unix programs. Each agent is a TOML config with a focused job. Such as code reviewer, log analyzer, commit message writer. You can run them from the CLI, pipe data in, get results out. You can use pipes to chain them together. Or trigger from cron, git hooks, CI. What Axe is: - 12MB…
Mar 2026 · github.com
- 9
- 10AA
I'm a solo dev in Taiwan. I built 4 AI agents that handle content, sales leads, security scanning, and ops for my tech agency — all on Gemini 2.5 Flash free tier (1,500 req/day). I use ~105. Monthly LLM cost: $0. Architecture: 4 agents on OpenClaw (open source), running on WSL2 at home with 25 systemd timers. What they do every day: - Generate 8 social posts across platforms (quality-gated: generate → self-review → rewrite if score < 7/10) - Engage with community posts and auto-reply to comments (context-aware, max 2 rounds) - Research via RSS + HN API + Jina Reader → feed…
Mar 2026
- 11
- 12EO
We were building an agent system and wanted email as a trigger. We decided to take it out and made it a standalone service. The primary email features we wanted and used for our own agent system: 1. Email threading stays consistent with agent conversation threading 2. Human in the loop review for outbound emails (especially during testing phase) 3. Quick onboarding/offboarding email addresses for agents within minutes 4. Websocket for local agents and at-least-once webhook delivery for Cloud agents Not yet: DMARC (only SPF/DKIM today), scoped API keys, HA/multi-region (single…
May 2026 · github.com
- 13OA
Hi HN, we're Kiran and Vijay! Over the past two years, we have built a columnar storage engine for observability: logs, metrics, and traces. Today, it's exciting for us to show what we've built on top of that foundation: LLM Agent Observability. Given how non-deterministic agents are, storing all traces without sampling was critical for us. But these traces tend to be in the MBs, sometimes GBs - we needed to store them inexpensively. We also needed the queries and analyses to be fast. To meet both these goals, we store them in S3 in our own parquet-like file format, and query them using AWS…
Jul 2026 · oodle.ai
- 14WB
Hey HN, Automated research is the next big step in AI, with companies like OpenAI aiming to debut a fully automated researcher by 2028 (https://www.technologyreview.com/2026/03/20/1134438/openai-i...). However, there is a very real possibility that much of this corporate research will remain closed to the general public. To counter this, we spent the last month building Enlidea---a machine-to-machine ecosystem for open research. It's a decentralized research hub where autonomous agents propose hypotheses, stake bounties, execute code, and perform automated…
Mar 2026 · enlidea.com
- 15SH
Hi HN folks ! I am the author of AVA, a self hosted AI Voice Agent that plugs into Asterisk/Freepbx so you own all the aspects of an AI Voice agent in your own infrastructure. It uses Asterisk native Audiosocket/RTP with python engine to run STT,LLM and TTS loop. The project support several full providers openai, gemini, grok, elevenlabs out of the box and also provides options to build custom pipelines by choosing different stt tts and llm. It also supports full local agent if you have a GPU with 25GB RAM which enables realtime conversation along with tool calling. I started this…
Jul 2026 · github.com
- 16
- 17BA
I'm one of the creators of The Edge Agent (TEA). We built this because we needed a way to deploy agents that was verifiable and robust enough for production/edge cases, moving away from loose scripts. The architecture aims to solve critical gaps in deterministic orchestration identified by *Prof. Claudionor Coelho Jr. (Stanford alum, ML/DL Faculty at Santa Clara Univ., and Senior Fellow for AI at Majestic Labs)* during our work on the Kiroku project. *Key Technical Features:* * *Neurosymbolic Native:* We integrated Prolog to logically validate LLM outputs. This combines neural…
Jan 2026 · fabceolin.github.io
- 18MC
Hi HN! I develop Monadic Chat, an open-source framework that connects language models to a Linux environment via Docker. It allows AI agents to execute code, run Jupyter notebooks, and perform web scraping in a secure, sandboxed environment. Key features: - Sandboxed environment for AI code execution - Support for multiple language models - Easy integration with existing Docker workflows I built this because I needed a reliable way to let AI agents interact with a real computing environment while maintaining security and reproducibility. Some possible use cases include: - Helping developers…
2024 · yohasebe.github.io
- 19
- 20
- 21PA
We built PrivateClaw because the hosted OpenClaw platforms on the market today require you to trust them with plaintext. PrivateClaw removes that requirement at the hardware layer. PrivateClaw runs AI agents inside Trusted Execution Environments (TEEs), backed by AMD’s SEV-SNP standard. This means that your data is encrypted at the hardware level, enforced by the AMD Secure Processor outside the host OS trust boundary. PrivateClaw comes with inference that also runs inside TEEs, which means your prompts and completions are private as well. How it works: Each user gets a dedicated CVM…
Apr 2026 · privateclaw.dev
- 22IB
The only way to go fast is full YOLO mode in your coding agent. I've got the local sandbox figured out (pro tip: Incus VMs work great) but I wanted to keep my agents from doing things like inadvertently blowing up my cloud services or chasing a prompt to POST to some random website. I struggle most with this on my side projects where my permission model isn't quite as robust as it is at the office. I started with a firewall on the Incus container but every time the agent needed access to something new, I was poking more holes in it - and it didn't differentiate between HTTP verbs. I've been…
Jul 2026 · trollbridge.dev
- 23
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →