i just built a 4-agent software team.

everything runs from Telegram and gets managed on a kanban board.

a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent.

the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know.

the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify.

the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer.

a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top.

an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast.

so the backend agent needs a backend built for agents, not for humans clicking through a dashboard.

that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill.

a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions.

to test the whole team, i had them build a working Google Docs clone, AI features included.

the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop.

the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside.

if you are building an AI backend engineer, InsForge is worth a look, it’s 100% open-source.

InsForge GitHub: https://github.com/InsForge/InsForge…

(don’t forget to star )

the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

InsForge/InsForge

Source: https://github.com/InsForge/InsForge

The all-in-one, open-source backend platform for agentic coding.

⭐ Help us reach more developers and grow the InsForge community. Star this repo!

InsForge

The all-in-one, open-source backend platform for agentic coding. InsForge gives your coding agent database, auth, storage, compute, hosting, and AI gateway to ship full-stack apps end-to-end.

https://github.com/user-attachments/assets/345efbc6-ca63-4189-bde0-12ef3bda561b

How it works

Coding agents interact with InsForge through one of two interfaces:

• MCP Server (self-hosted and cloud): exposes InsForge’s operations as tools any MCP-compatible agent can call.
• CLI + Skills (cloud only): a command-line interface paired with Skills that agents invoke directly from the terminal.

Both interfaces let coding agents operate the backend like backend engineers:

• Read backend context and state: Pull documentation, schemas, metadata (deployed functions, bucket contents, auth config), and runtime logs, so the agent has what it needs to write code, verify what it built, and debug when something breaks.
• Configure primitives: Deploy edge functions, run database migrations, create storage buckets, set up auth providers, and configure other backend resources directly.

graph TB

    subgraph TOP[" "]
        AG[AI Coding Agents]
    end

    subgraph MID[" "]
        SL[InsForge]
    end

    AG --> SL

    SL --> AUTH[Authentication]
    SL --> DB[Database]
    SL --> ST[Storage]
    SL --> EF[Edge Functions]
    SL --> MG[Model Gateway]
    SL --> CP[Compute]
    SL --> DEP[Deployment]

    classDef bar fill:#0b0f14,stroke:#30363d,stroke-width:1px,color:#ffffff
    classDef card fill:#161b22,stroke:#30363d,stroke-width:1px,color:#ffffff

    class AG,SL bar
    class AUTH,DB,ST,EF,MG,CP,DEP card

    style TOP fill:transparent,stroke:transparent
    style MID fill:transparent,stroke:transparent

    linkStyle default stroke:#30363d,stroke-width:1px

Core Products:

• Authentication: User management, authentication, and sessions
• Database: Postgres relational database
• Storage: S3 compatible file storage
• Model Gateway: OpenAI compatible API across multiple LLM providers
• Edge Functions: Serverless code running on the edge
• Compute (private preview): Long-running container services
• Site Deployment: Site build and deployment

⭐️ Star the Repository

If you find InsForge useful or interesting, a GitHub Star ⭐️ would be greatly appreciated.

Quickstart

Cloud-hosted: insforge.dev

Self-hosted: Docker Compose

Prerequisites: Docker + Node.js

1. Setup

You can run InsForge locally using Docker Compose. This will start a local InsForge instance on your machine.

Or run from source:

# Run with Docker
git clone https://github.com/InsForge/InsForge.git
cd insforge
cp .env.example .env
docker compose -f docker-compose.prod.yml up

2. Connect InsForge MCP

Open http://localhost:7130

Follow the steps to connect InsForge MCP Server

3. Verify installation

To verify the connection, send the following prompt to your agent:

I'm using InsForge as my backend platform, call InsForge MCP's fetch-docs tool to learn about InsForge instructions.

4. Running Multiple Projects

You can run multiple InsForge projects on the same host by using different ports and project names.

# Create a separate env file for each project
cp .env.example .env.project1
cp .env.example .env.project2

Edit .env.project2 with different ports:

POSTGRES_PORT=5442
POSTGREST_PORT=5440
APP_PORT=7230
AUTH_PORT=7231
DENO_PORT=7233

Start each project with a unique name:

docker compose -f docker-compose.prod.yml --env-file .env.project1 -p project1 up -d
docker compose -f docker-compose.prod.yml --env-file .env.project2 -p project2 up -d

Each project gets its own isolated database, storage, and configuration. Manage them with:

docker compose -f docker-compose.prod.yml --env-file .env.project1 -p project1 ps      # status
docker compose -f docker-compose.prod.yml --env-file .env.project1 -p project1 logs -f  # logs
docker compose -f docker-compose.prod.yml --env-file .env.project1 -p project1 down     # stop

One-click Deployment

In addition to running InsForge locally, you can also launch InsForge using a pre-configured setup. This allows you to get up and running quickly with InsForge without installing Docker on your local machine.

Railway	Zeabur	Sealos

Contributing

Contributing: If you’re interested in contributing, you can check our guide here CONTRIBUTING.md. We truly appreciate pull requests, all types of help are appreciated!

Support: If you need any help or support, we’re responsive on our Discord channel, and also feel free to email us [email protected] too!

Documentation & Support

Documentation

• Official Docs - Comprehensive guides and API references

Community

• Discord - Join our vibrant community
• Twitter - Follow for updates and tips

Contact

• Email: [email protected]

License

This project is licensed under the Apache License 2.0 - see the LICENSE file for details.

Badges

Show your project is built with InsForge.

Made with InsForge

Markdown:

[![Made with InsForge](https://insforge.dev/badge-made-with-insforge.svg)](https://insforge.dev)

HTML:

<a href="https://insforge.dev">
  <img
    width="168"
    height="30"
    src="https://insforge.dev/badge-made-with-insforge.svg"
    alt="Made with InsForge"
  />
</a>

Made with InsForge (dark)

Markdown:

[![Made with InsForge](https://insforge.dev/badge-made-with-insforge-dark.svg)](https://insforge.dev)

HTML:

<a href="https://insforge.dev">
  <img
    width="168"
    height="30"
    src="https://insforge.dev/badge-made-with-insforge-dark.svg"
    alt="Made with InsForge"
  />
</a>

⭐ Star us on GitHub to get notified about new releases!