Scylla is a modular framework for Unity that replaces disconnected assets and fragile glue code with a single, coherent architecture. Utils, Events, Input, UI, graphics, cameras, stats, in-game debug console, data pipelines, and much more, designed from the ground up to work together.
If you ever lost track of your game project because too many third-party systems made you lose focus while stitching together half a dozen unrelated assets every time you start a project then Scylla is for you. Scylla gives you one foundation, one set of rules, and one way of doing things across every system you build on. The pieces fit because they were made to fit, not because someone wrote an adapter on a Friday night.
Why Scylla
Most of us have shipped a Unity project held together with a handful of assets from a handful of authors. Each one has its own lifecycle, its own config format, its own opinion about how things should work. The first weeks feel productive. The next few months get spent making them coexist.
Scylla starts from the other end. One framework, one set of rules, one way of doing things, applied consistently from the lowest utility to the highest gameplay system. Add a module and you add a seamless feature, not a new dialect to learn.
Built by a game developer, for game developers
No enterprise patterns shoved into engine code. No academic abstractions. The whole point is to keep you working on the part of the game that players will actually experience, and out of the part where five unrelated systems are arguing about who owns the update loop.
Scylla is opinionated where opinions matter (lifecycle, dependency direction, error handling) and quiet where they do not (you write your gameplay code the way you want to write it). The framework holds the scaffolding. You build the game on top.
Why use it
- One framework, not a dozen assets glued together. Shared lifecycle, shared events, shared configuration, shared logging. Nothing fights for control.
- Predictable from the first frame. Startup is deterministic. If something is missing or misconfigured, you find out at boot, not three scenes in.
- Built for real games. Every part of Scylla earns its place on actual projects. No demoware, no abandoned half-features.
- Independent modules. Use one. Or use all of them. The framework does not push back when you say no.
- Performance-minded from the ground up. No hidden Update loops, no surprise allocations, no zombie systems burning frames when you are not using them.
- Honest engineering. Fail-fast validation, clear errors, no magic resolution. If something breaks, the stack trace points at the actual problem.
- Designed to scale with your project. Prototype with one module. Ship a full game on the entire stack. The architecture does not change underneath you.
- Familiar everywhere. Once you understand how one part of Scylla works, you understand how all of it works.
The shape of it
Underneath, Scylla is a layered framework. A core sits at the bottom and provides the things every module needs: lifecycle, events, configuration, logging, and a broad utility library. Above the core, modules slot into three tiers. Foundational systems that almost every game needs. Feature systems that most games eventually need. Gameplay systems aimed at specific features or genres.
Dependencies only ever flow downward. A higher-tier module can build on a lower-tier one. The reverse is impossible by design. That single rule is what keeps the whole framework predictable as it grows, and it is why you can swap or skip pieces without anything quietly breaking somewhere else.
Get back to making your game
You came to Unity to build games, not to wire systems together. Scylla is the framework that gets out of your way.