u/Consistent-Stock9034

Building complex apps without code right now usually means managing a nightmare stack. You use one tool for the frontend, n8n for the logic, another for the database, and custom cloud functions to glue it all together.

When one API breaks, the whole house of cards falls down.

I got tired of managing fragmented workflows, so I built Fleeks.

Fleeks isn't another visual node builder. It’s a cloud execution workspace. You get an AI agent that actually writes, runs, and deploys real custom software in one isolated environment.

In the raw video attached, you can see how it works under the hood:

1. You describe what you want the app or backend to do.
2. We instantly spin up an isolated cloud computer. The agent writes the code, runs the server, and tests the output.
3. If it crashes, the agent reads the terminal logs and fixes the bug autonomously.

The Superpower: We integrated 270+ MCP tools into the platform out of the box. Instead of you dragging nodes around in n8n to connect APIs, the agent natively talks to your external data and services to build the workflow for you.

Instead of chaining together five different no-code tools, the agent builds you a custom backend and deploys it.

We are already open and live in Beta. I’ve included enough free tokens for you to take those messy, unfinished projects you've been duct-taping together and deploy them in the cloud to see if they actually hold up.

Try it here: fleeks.ai

I’m looking for honest feedback on the workflow—give it a spin and tell me exactly where the agent succeeds or where the infrastructure needs more work.

Building an AI agent is the easy part now. Anyone can do it in an afternoon. But the moment you want it running permanently in the background, actually connected to your stack, doing real work while you sleep, that's where everything falls apart. You end up spending more time on the microservice hosting the agent than on the agent itself. The logic takes a day. The plumbing takes a week and then breaks on a Tuesday for no reason.

I kept hitting that same wall. Eventually I stopped complaining about it and started building https://fleeks.ai/.

You build your agent locally, test it, make sure it behaves the way you want. Then you run fleeks promote. It goes live on Fleeks infrastructure and runs 24/7. No server to spin up, no containers to manage, no babysitting.

The other thing that makes this different is native MCP support, which means your agents connect to AWS, Kubernetes, GitHub, Postgres, PagerDuty without you writing a single integration. The agent figures out the API calls itself based on what you tell it to do.

We use it internally for autonomous incident response. A deployment fails, the agent catches it, traces the root cause, patches the config, and opens a PR before anyone gets paged. That loop runs without us.

Fleeks is fully open-source. You can audit everything it does locally before you promote anything to the cloud, and you can run the whole engine inside your own VPC if you need full control.

Would love feedback from anyone who's tried to solve this hosting problem themselves. What did your setup look like before?