https://github.com/crmkit/crmkit

So far so good.

This is what I did with this project https://github.com/crmkit/crmkit/ and to be honest the approach grows on me and fits well if you are a backend person.

That being said, while I am biased, there is a lot of work around infrastructure so calling it "just a wrapper" massively underestimates the effort - this is purely from my own experience building this space.

Besides, if it is true how come OpenClaw is spending so much money on a open source project. Salaries alone will cost 7 digit sum for a harness and I have first hand experience dealing with companies doing exactly this.

Shameful plug - we are building cbk.ai, better known today as chatbotkit.com.

Also this is a game has very simple mechanics I am sure you can generate as easily with Cursor or some other tools.

Today AI is 100% automating the software engineering market. We all know it and it is not evenly distributed with some fields being more impacted than others.

However, what is not mentioned anywhere is for long this will continue and what shape it will take. It is a trickier question.

There are two factors in my mind: cost and volume.

On the cost side, AI coding agents could become unfordable. What happens then? Back to engineering jobs? Hard to tell. It might impact seriously the bottom line of many companies while jobs remain lost forever.

On the scale side, the more code is written the more complex it becomes - that is a fact. Who is going to look after this code? More AI? That will make it more costly. Or is that most software is dead on arrival - then why build it?

So it is not clear cut. The investment is there but how to turn the investment in meaningful long-term ROI is not.

Even on the highly subsidies plans most software written today has marginal ROI. Building landing pages and features that nobody asked for is not a good execution plan and frankly I have done this mistake myself.

The last bit I would like to flag is that if software becomes almost free then why build at all? Why would companies even bother building anything at all?

Reliable means "can it finish the job that was tasked to do". It certainly has nothing to do with state machines.

And this is far much common then one might think and classic problem across the board. There are easy solutions too.

That's it. I will report back if it works.

However, I can share what we did to ease on our GitHub Actions bills if it helps.

Effectively we have our own runners hooked so that a job is scheduled, a runner picks it up and goes with it. We still use GitHub Actions but our monthly bill is now flat because we pay for a server. It is about 6x cheaper if not more.

The solution is not open source but it boils down to a Go service that orchestrates firecracker vms. All the vms are pre-warmed so there is always a fresh supply of workers to pick jobs of various sizes.

It is basic and it works. We have not had any issues since deployed.

The runners can be anything from 1 cpu 2 GB to 64GB 8 cpus. We can add more worker types in a config file.

I am not exaggerating when I say that we used to pay 1000s per month for this. Now our bills are in the range of a few hundred. Other dev boxes are done in the same way.