Modern .NET ecosystem tooling for realtime systems, graphics, runtime infrastructure, experimentation, and whatever else seems like a good idea at 02:00.
The name was designed to feel:
- modern, but not trendy
- technical, but still human
- platform-oriented, not product-oriented
- professional without sounding corporate
- memorable without needing abbreviations
Novo subtly hints at ideas like:
- renewal
- iteration
- evolution
- modern systems
while -olis was chosen mostly because it sounds structured, calm, and conversationally natural.
Importantly:
"we use Novolis.Hosting internally"
sounds like software infrastructure, not a crypto exchange or an anime MMO.
That matters 😄
Novolis projects aim to be:
- easy to pronounce
- easy to remember
- pleasant to say in meetings
- usable in both OSS and enterprise environments
We intentionally avoid names that sound like:
- 🚀 startup buzzwords
- 🪙 crypto projects
- 🧙 fantasy spellbooks
- 🔥 “next-gen ultra hyper” frameworks
The long-term idea is an ecosystem of modular packages and tooling:
Novolis.Raylib
Novolis.Hosting
Novolis.Game
Novolis.Native
Novolis.Gui
and potentially much more over time.
The ecosystem is intentionally broad and technology-neutral.
Games, tools, rendering, simulation, diagnostics, networking, experiments — all fair game.
Some recurring themes:
- progressive complexity
- composable architecture
- modern .NET patterns
- low ceremony
- native escape hatches
- practical developer experience
No forced mega-engine architecture.
No mandatory ECS religion.
No “you must do things our way” energy.
Novolis is built openly, iteratively, and experimentally.
Ideas, feedback, prototypes, discussions, and weird experiments are welcome.
| Resource | Link |
|---|---|
| Contribution policy | novolis-governance |
| Security policy | SECURITY.md |
| Package registry | novolis-registry |
| Roadmap | roadmap.md |
| Governance | novolis-governance |
| .NET repo template | novolis-template-dotnet |