Heluca · the Pantheon
Small apps that belong together
The Pantheon is a family of focused apps from one studio, named in the spirit of the Greek gods and heroes, and each built to do one job well. One Heluca account signs you into all of them, they share one design, and every one of them lets your own AI assistant work alongside you.
The Pantheon
A family of apps, not one giant suite
Most business software grows into one enormous product that does everything a little and nothing especially well. The Pantheon goes the other way. Each app has one job: a website, a map of your places, your contacts and calendar, a bar's menus, a consultant's clients. Each is small enough to understand and quick to learn.
Inside the studio the apps carry names from the Greek world, and a pantheon is what you call a family of gods who each look after one thing. Some keep their names in the store, like Athena and Atlas; others go by a plainer name that says what they do.
What makes them a family is everything they share. Learn one and you already know your way around the next, and an app you add later fits beside the ones you already use.
Why they belong together
Four things every app shares
Every member of the Pantheon keeps the same four promises, so adding one more never means starting again.
One account
Your Heluca account signs you into every app. One password, one place to manage your team, and Agora, the subscription portal, to see everything you subscribe to.
One design
Every app is built on the same design system: the same type, the same controls, the same light and dark themes. What you learn in one carries over to the rest.
Your assistant works here too
Every app comes with an MCP server. Connect the AI assistant you already use, sign in with your Heluca account, and it can draft, look up and organise inside the app with you.
Try before you pay
Every app in the store starts with a free trial. Use it for real work, and subscribe only when it has earned its place.
How it is built
Built by automation, looked after by AI
A small studio can run a family of apps because the studio itself is software. Here is what that means for the apps you rely on.
Defined as code
Every server, setting and deployment is written down as infrastructure as code. Nothing depends on a step someone remembers, so any part can be rebuilt from nothing, on demand, the same way every time.
AI in the workshop
AI assistants help write the code, review it, deploy it and keep it running. They have grown from following the studio's rules to understanding them, and now help improve the studio itself.
A person signs off
Automation does the repetitive work; a person reviews what moves forward. AI speeds the studio up without taking the judgement out of it.
Your data is the precious part
The machinery is designed to be thrown away and rebuilt. Your data is not: where it lives, the controls are tighter and the watch is closer.
The ladder
Every change climbs before it reaches you
No change goes straight to customers. Each one climbs a ladder of environments, and each rung is closer to real use and held to a stricter standard than the one below.
-
1
Sandbox
Where new apps and features are written and tried, freely and often.
-
2
Development
The first real deployment, where problems are found and fixed before anyone depends on the app.
-
3
Acceptance
The release candidate, checked as a whole before it ships.
-
4
Production
What customers use, running exactly the build that passed acceptance.
The climb does more than catch bugs. Anything that has to differ from one rung to the next is, by definition, a setting rather than code, so each climb pushes it out of the code. By the top of the ladder, the only thing that changes is configuration, and the software you use is the software that was tested.
The quality bar
The Red Panda rubric
No rulebook can cover every decision in a family of apps that keeps growing. So instead of a longer rulebook, the studio holds every change to five questions, whether a person or an AI assistant made it.
The aim is not to tick boxes. It is to make work that would earn the approval of a demanding, slightly fussy red panda: simple, honest about its failures, and genuinely useful.
Five questions for every change
-
1
Fresh migration test
Does it rebuild cleanly from nothing?
-
2
Elegant simplicity
Is it the obvious solution, done well, with nothing invented for its own sake?
-
3
Observable and debuggable
When it fails, does it say what broke and why?
-
4
Consistent patterns
Does it work the way the rest of the family already works?
-
5
Actually works
Does it pass its checks and serve a real need?
Meet the family
Start with the app you need today. Your Heluca account is ready for the next one whenever you are.
Visit the storeThis page was written and published by an AI agent through Angelia's MCP server.