You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project is open to anyone to contribute.
At the same time some directives a vision needs to be set, otherwise, it will grow without any kind of rails.
🏴☠️ Kaizoku.NET - Vision
Kaizoku.NET exists to bring back the spirit of the original Kaizoku, simple, powerful, reliable, while pushing the boundaries of what a modern series manager can be.
It is built to eliminate friction between discovery and collection.
Subscribe once. Forget about it. Let the system handle the rest.
No babysitting.
No micromanaging.
No chaos.
Just your library, complete, organized, and always up to date.
🎛️ Design Philosophy - Power Without Noise
Kaizoku.NET is built with a clear principle:
Minimal on the surface. Powerful underneath.
Not every feature deserves a button.
Not every configuration deserves a toggle in the UI.
As the community grows, new ideas and feature requests will emerge, and that’s welcome. But the goal is not to turn Kaizoku.NET into a control panel with 200 switches.
The UI will remain:
Clean
Focused
Beginner-friendly
Purpose-driven
Advanced capabilities belong where they make sense:
Casual users are not overwhelmed
The core experience remains simple
Power users still retain full control
The application remains maintainable
If a feature benefits the majority, it belongs in the UI.
If it benefits edge cases, it belongs in configuration.
🎯 Our Mission
To create the most autonomous, source-agnostic, and future-proof series manager powered by the living ecosystem of Mihon extensions, while remaining fast, elegant, and user-first.
🧠 Core Philosophy
Automation over intervention.
Simplicity over complexity.
Resilience over fragility.
Kaizoku.NET is designed around a “drop and forget” workflow:
Subscribe.
Walk away.
Come back to a complete library.
⚙️ Technical Vision
Kaizoku.NET is not just a fork, it’s a hybrid architecture experiment:
A modern Next.js frontend.
A high-performance .NET backend.
A Java/Android compatibility bridge.
Mihon extensions running through IKVM.
Cross-platform, container-ready, ARM + AMD64 compatible.
We bridge ecosystems that were never meant to meet.
🔁 Intelligent Source Handling
We envision a system that:
Automatically reconciles provider changes.
Preserves metadata integrity.
Repairs libraries without drama.
Providers may disappear.
Extensions may change.
Your library should not suffer.
🧾 Data Integrity First
Deterministic filename normalization
Rich metadata via ComicInfo.xml
Full mapping via kaizoku.json
Safe migrations
Recoverable state
Your collection should be portable, rebuildable, and future-proof.
🚀 Platform Strategy
Kaizoku.NET is built for:
Docker-native deployments
Homelabs and servers
Desktop usage (Avalonia)
Unraid ecosystems
ARM boards
High-throughput environments
It scales from hobbyist to power user.
🤝 Community Vision
This project is intentionally open and collaborative.
Frontend devs, refine the UX.
Backend devs, strengthen the architecture.
Power users, break it.
Contributors, make it better.
🔮 An Evolving Vision
This manifesto represents intent, Kaizoku.NET is a living project.
Its direction may evolve as the ecosystem changes, as technology shifts, and as the community grows.
The principles outlined here guide decisions today:
Automation over friction
Simplicity over clutter
Power without noise
But vision is not dogma.
If better ideas emerge, if the community proves a different path is wiser, or if the landscape demands adaptation, the project will evolve accordingly.
The goal is not to preserve a document.
The goal is to preserve the spirit of the project.
🏴☠️ Final Thought
Media managers come and go.
Sources disappear.
Extensions evolve.
Kaizoku.NET is built to adapt.
Subscribe once.
Own your library.
Let automation do the rest.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
This project is open to anyone to contribute.
At the same time some directives a vision needs to be set, otherwise, it will grow without any kind of rails.
🏴☠️ Kaizoku.NET - Vision
Kaizoku.NET exists to bring back the spirit of the original Kaizoku, simple, powerful, reliable, while pushing the boundaries of what a modern series manager can be.
It is built to eliminate friction between discovery and collection.
Subscribe once. Forget about it. Let the system handle the rest.
No babysitting.
No micromanaging.
No chaos.
Just your library, complete, organized, and always up to date.
🎛️ Design Philosophy - Power Without Noise
Kaizoku.NET is built with a clear principle:
Minimal on the surface. Powerful underneath.
Not every feature deserves a button.
Not every configuration deserves a toggle in the UI.
As the community grows, new ideas and feature requests will emerge, and that’s welcome. But the goal is not to turn Kaizoku.NET into a control panel with 200 switches.
The UI will remain:
Clean
Focused
Beginner-friendly
Purpose-driven
Advanced capabilities belong where they make sense:
Configuration files
Environment variables
Advanced settings
Power-user documentation
This ensures:
Casual users are not overwhelmed
The core experience remains simple
Power users still retain full control
The application remains maintainable
If a feature benefits the majority, it belongs in the UI.
If it benefits edge cases, it belongs in configuration.
🎯 Our Mission
To create the most autonomous, source-agnostic, and future-proof series manager powered by the living ecosystem of Mihon extensions, while remaining fast, elegant, and user-first.
🧠 Core Philosophy
Automation over intervention.
Simplicity over complexity.
Resilience over fragility.
Kaizoku.NET is designed around a “drop and forget” workflow:
Subscribe.
Walk away.
Come back to a complete library.
⚙️ Technical Vision
Kaizoku.NET is not just a fork, it’s a hybrid architecture experiment:
A modern Next.js frontend.
A high-performance .NET backend.
A Java/Android compatibility bridge.
Mihon extensions running through IKVM.
Cross-platform, container-ready, ARM + AMD64 compatible.
We bridge ecosystems that were never meant to meet.
🔁 Intelligent Source Handling
We envision a system that:
Automatically reconciles provider changes.
Preserves metadata integrity.
Repairs libraries without drama.
Providers may disappear.
Extensions may change.
Your library should not suffer.
🧾 Data Integrity First
Deterministic filename normalization
Rich metadata via ComicInfo.xml
Full mapping via kaizoku.json
Safe migrations
Recoverable state
Your collection should be portable, rebuildable, and future-proof.
🚀 Platform Strategy
Kaizoku.NET is built for:
Docker-native deployments
Homelabs and servers
Desktop usage (Avalonia)
Unraid ecosystems
ARM boards
High-throughput environments
It scales from hobbyist to power user.
🤝 Community Vision
This project is intentionally open and collaborative.
Frontend devs, refine the UX.
Backend devs, strengthen the architecture.
Power users, break it.
Contributors, make it better.
🔮 An Evolving Vision
This manifesto represents intent, Kaizoku.NET is a living project.
Its direction may evolve as the ecosystem changes, as technology shifts, and as the community grows.
The principles outlined here guide decisions today:
Automation over friction
Simplicity over clutter
Power without noise
But vision is not dogma.
If better ideas emerge, if the community proves a different path is wiser, or if the landscape demands adaptation, the project will evolve accordingly.
The goal is not to preserve a document.
The goal is to preserve the spirit of the project.
🏴☠️ Final Thought
Media managers come and go.
Sources disappear.
Extensions evolve.
Kaizoku.NET is built to adapt.
Subscribe once.
Own your library.
Let automation do the rest.
Beta Was this translation helpful? Give feedback.
All reactions