The Story
The story of Magic Cat Engine can't be told without telling a little bit about myself. The short story is I got very sick, psychologically, but found a way of building applications that was one hundred percent no code. I ended up in hospital, but the technology stayed with me, and with AI I tried to tackle it, but it wasn't until Claude Code produced a working demo that I finally realized I had a real find in the middle of misery and madness.
How It Works
Magic Cat Engine feels like a lot to take in, you're working with all these different languages at once. The idea is simple, keep it as close to no code as possible, but I did place a zone where people can put all the code they want in.
Events
First you have events, events you create to be fired at different instances, any of the machines in the system can listen in for events and do something when that event is fired.
Database & Pipes
Next you have the database and Pipes, pipes simply connect you right to the database. You create a pipe and that does a POST or a GET.
Machines
Then there are Machines. Every visual element you see on the page is a Machine — a button, a text input, an image, a list. Machines are the building blocks of everything. Each one can listen for events, respond to data coming through a pipe, or send out events of its own. They talk to each other through Wires.
Wires
Wires are how Machines share information. You connect one Machine to another and the data flows between them automatically. Change a value in one place and everything wired to it updates. No code required, no refresh needed. The idea was always that a person should be able to look at the screen and see the shape of how the application works, the way you might look at plumbing and understand where the water goes.
Loops
Loops came out of a simple problem — what do you do when you have a list of things? A list of products, a list of messages, a list of anything. A Loop takes a pipe, takes that data coming back, and automatically stamps out a Machine for each item. You design one, and the Loop handles the rest. It was one of those moments in development where something clicked into place so cleanly it almost felt like cheating.
Views
Views handle pages. When your application needs to show different screens depending on where the user is — a home page, a profile page, a settings page — Views manage that routing. The URL changes, the right content appears, and the whole thing stays inside that single file.
One File
And that single file is the point. Everything Magic Cat Engine produces is one standalone HTML file. No server required to run it, no framework to install, no dependencies to manage. You can put it on a USB stick. You can email it. You can open it ten years from now and it will still work. That felt important to me, especially building this the way I did — in hospital, on borrowed time, with no guarantee of infrastructure or stability. The output had to be something that could survive on its own.
Logic Panel
Finally there's the Logic Panel. This is where the no-code meets the can-code. The Logic Panel is a visual if-else system — you set up conditions, you define what happens when they're true, what happens when they're not. For most things that's enough. But if you need to go further, if you need to write actual JavaScript, there's a zone for that too. I didn't want to make a system that imprisoned people. I just wanted the door to be optional.
The whole thing is held together by one philosophy: the application should be readable by looking at it. Not at the source code, not at a terminal, not at a spreadsheet of configuration. At the screen itself. That was the dream I carried through some very dark places. I'm glad it made it out the other side.