The Skene open stack
When we talk about the open stack, we mean the parts of Skene that live in public: tools, schemas, and utilities that you can inspect, fork, and run without touching the product surface.
What “open stack” means here
The open stack is not a separate product. It is a set of building blocks we publish in the open when they are useful on their own: analyzers, generators, injectors, components, and the schemas that tie them together.
The goal is to make the underlying mechanics visible. You should be able to see how we think about growth infrastructure, not just the surface in the main Skene app.
What is published openly
Over time, the open stack will include:
- Code for tools that are useful outside of Skene itself.
- Schemas and manifest formats, such as the growth manifest.
- Small utilities that make it easier to run or reason about loops.
- Reference diagrams or examples that clarify how pieces fit together.
The concrete projects live on the open source page, where each one is listed with a short description and current status.
How maturity works
Not every repository in the open stack is equally stable. We use simple maturity labels to make that obvious without turning this page into a roadmap.
- Experiment: active exploration. APIs or behavior can change quickly.
- Maintained: used in real work, kept in a working state with fixes and small improvements.
- Archived: kept for reference. Not removed, but not expected to evolve.
These labels are descriptive, not promises. They exist so you can decide how much to rely on something in your own stack.