It took me 18 months to build a Backend Architecture-as-a-Service platform. I need your help testing it and giving me your honest feedback.
▲ 20 r/AISystemsEngineering+7 crossposts

It took me 18 months to build a Backend Architecture-as-a-Service platform. I need your help testing it and giving me your honest feedback.

You simply describe the backend behavior you want in plain language; AI handles code, tests, docs, database, and CI/CD pipelines. Then you can test them and deploy them on staging and production.

You don't need to think about infra and maintaining anything. Everything is fully managed in the platform, from the database to CI/CD pipelines.

I really need your help. Could you please check it out, try to build something real, and give me your honest feedback?

Check it out: baasforge.com - and if you're curious, the docs are here: baasforge.com/docs

If you have any questions, shoot them.

u/yousefemz — 7 days ago

18 months in: prompt to deployed backend, no git, no IDE, no server config

The software we worked on for 18 months is ready. Its purpose is writing backend projects with AI without needing to write code directly.

With this software there's no need for Git and change management, everything is built inside one platform, from starting the code to deploying on stage and production and debugging and monitoring.

If I want to explain it in one line, it goes like this:

You can build and deploy backend from zero to a hundred in one platform with prompts, and get automatic documentation.

The code structure it writes for you is organized and scalable and maintainable, it writes code based on DDD and arranges everything neatly for you from the very start, all the code goes through 4 stages of lint and rule and compiler check and all the code is written uniformly, though you don't have direct access to writing code at all and whatever you need you have to tell the AI and it does it for you.

There's no need for a database and an SDK has been written specifically for the platform, and it handles working with the database and Rabbit and NATS and these kinds of tools for you, and you don't get involved with the config and maintenance of these tools either.

The code is written in Node.js, but it doesn't run in a Node.js environment because of the heavy RAM consumption in Node.js, so a runtime similar to Cloudflare Worker has been implemented (similar to AWS Lambda), and the cold start of what we have is close to Cloudflare Worker and is about 200ms, meaning it's faster than AWS Lambda. This runtime is written in a way that it can handle several million files, something that definitely isn't possible with Node.js.

Overall it has the entire stack of a relatively mid-level backend project automatically and you don't need any other tool.

Its difference with Insforge is that you don't need to have a Cursor, you don't need to have Supabase, you don't need to pay several times, and also because the platform is unified and everything is in it, both the costs become much lower, and project management becomes simpler and more organized, and we can also provide much stronger monitoring.

Its difference with Cursor is that you don't get involved with getting a server and configuring it, you don't get involved with CI/CD either, and you also don't get involved with monitoring and debugging and everything is ready in the platform.

Its difference with Supabase is that the AI is integrated and a very good chat has been built into the platform itself and you can tell it to write the code for you without needing Cursor. This chat works like Cursor, it has several different tools, it has several sub agents that break the work down and split it up so they can write more accurate code.

Its difference with Replit is that this platform is dedicated to backend and gives you much better monitoring and debugging, also Replit brings up each project as a container which has much higher RAM consumption, so the final cost for several million users on Replit is much higher than several million users on my platform because of the very large infrastructure difference they have.

The LLM model used is Gemini Flash Lite 3.1, meaning it comes out much cheaper compared to Sonnet which is the advantage of this project, and it's optimized so that it can write and debug code well with ordinary AI models, which makes the final cost per user much lower than other platforms.

reddit.com
u/yousefemz — 28 days ago

After 18 months, my backend architecture platform is finally ready.

The software we worked on for 18 months is ready. Its purpose is writing backend projects with AI without needing to write code directly.

With this software there's no need for Git and change management, everything is built inside one platform, from starting the code to deploying on stage and production and debugging and monitoring.

If I want to explain it in one line, it goes like this:

You can build and deploy backend from zero to a hundred in one platform with prompts, and get automatic documentation.

The code structure it writes for you is organized and scalable and maintainable, it writes code based on DDD and arranges everything neatly for you from the very start, all the code goes through 4 stages of lint and rule and compiler check and all the code is written uniformly, though you don't have direct access to writing code at all and whatever you need you have to tell the AI and it does it for you.

There's no need for a database and an SDK has been written specifically for the platform, and it handles working with the database and Rabbit and NATS and these kinds of tools for you, and you don't get involved with the config and maintenance of these tools either.

The code is written in Node.js, but it doesn't run in a Node.js environment because of the heavy RAM consumption in Node.js, so a runtime similar to Cloudflare Worker has been implemented (similar to AWS Lambda), and the cold start of what we have is close to Cloudflare Worker and is about 200ms, meaning it's faster than AWS Lambda. This runtime is written in a way that it can handle several million files, something that definitely isn't possible with Node.js.

Overall it has the entire stack of a relatively mid-level backend project automatically and you don't need any other tool.

Its difference with Insforge is that you don't need to have a Cursor, you don't need to have Supabase, you don't need to pay several times, and also because the platform is unified and everything is in it, both the costs become much lower, and project management becomes simpler and more organized, and we can also provide much stronger monitoring.

Its difference with Cursor is that you don't get involved with getting a server and configuring it, you don't get involved with CI/CD either, and you also don't get involved with monitoring and debugging and everything is ready in the platform.

Its difference with Supabase is that the AI is integrated and a very good chat has been built into the platform itself and you can tell it to write the code for you without needing Cursor. This chat works like Cursor, it has several different tools, it has several sub agents that break the work down and split it up so they can write more accurate code.

Its difference with Replit is that this platform is dedicated to backend and gives you much better monitoring and debugging, also Replit brings up each project as a container which has much higher RAM consumption, so the final cost for several million users on Replit is much higher than several million users on my platform because of the very large infrastructure difference they have.

The LLM model used is Gemini Flash Lite 3.1, meaning it comes out much cheaper compared to Sonnet which is the advantage of this project, and it's optimized so that it can write and debug code well with ordinary AI models, which makes the final cost per user much lower than other platforms.

reddit.com
u/yousefemz — 28 days ago
▲ 2 r/AiBuilders+1 crossposts

18 months ago we weren't sure it was possible. Today we launched it.

We kept asking ourselves one question for a year and a half: can an AI actually design a scalable backend from a description of how it should behave, not demo-ware, something that holds up in production?

We didn't know. Some weeks it felt like the answer was no, or that we'd end up with code that looks right and falls apart the second real traffic hits it.

We just launched it. You describe how your backend should behave, schema, auth, endpoints, whatever, and it builds the architecture and deploys it to staging and production.

It's early. There are rough edges we haven't smoothed out yet. That's exactly why I'm posting here instead of just quietly shipping it.

Go check it out and give me your honest thoughts. That's the feedback that matters, not "cool idea," but where it actually falls short.

Check the link below. Happy to answer anything about how it works.
BaaSForge

u/yousefemz — 1 month ago