Helm — An Extensible, Plugin-First Fleet & Corp Management Platform (Beta, Open Source)
Hey everyone,
I’ve been building Helm — an open-source EVE Online corporation and fleet management platform designed around a single core idea: the platform itself should stay minimal, and everything interesting should live in plugins.
GitHub: GitHub - Jerry-Scintilla/Helm: 一个开源的轻量化eve军团管理项目 · GitHub
Screenshots
What makes Helm different?
Most corp tools are monolithic — you get a fixed feature set, and adding something new means forking the whole project or waiting for the maintainer. Helm is built the other way around.
A forgiving plugin framework
Helm plugins are standard Python packages that subclass a single base class (HelmPlugin). A plugin can contribute any combination of:
-
API routes (FastAPI routers, registered automatically)
-
Database models (SQLAlchemy 2.0, async — migrations included via Alembic)
-
Background tasks (Celery workers, with Redis-backed scheduling)
-
RBAC permissions (fine-grained, per-plugin)
-
Sidebar navigation items
-
A compiled Vue 3 frontend (bundled into the plugin package itself)
The framework is deliberately lenient. You don’t have to implement everything — a plugin that only adds two API endpoints and nothing else is perfectly valid. The core doesn’t care.
Hot-plug design
Plugins are installed, enabled, and disabled at runtime through the Plugin Marketplace UI — no server restart required (for most changes). The plugin index is community-maintained and pulls live updates. If you build something useful, submitting it to the index is a one-PR process.
Built for vibe coding
Helm’s plugin API is designed to be easy to scaffold and iterate on quickly. The full plugin development guide walks you through generating a working skeleton in minutes. Because each plugin is an isolated Python package, you can develop and test yours locally without touching the core codebase at all. The barrier to shipping a useful feature is intentionally low.
The ecosystem is the product
The thin core (auth, ESI pipelines, permissions, real-time SSE) is stable. Everything else — skill tracking, fleet composition tools, doctrine checkers, killboard integrations, SRP workflows, recruitment portals — is fair game for the community to build. The goal is an ecosystem of small, focused plugins rather than one giant tool that tries to do everything.
Current status
Helm is in beta (v0.1.0). The core is running, Docker deployment works, and a handful of plugins already exist. It’s ready for early testers and contributors.
Tech stack: Python 3.12 / FastAPI / SQLAlchemy 2.0 (async) / Celery + Redis / Vue 3 + Vite / PostgreSQL / EVE SSO OAuth2
What I’m looking for
Feature requests & use cases — What does your corp actually need? What tools do you wish existed? I want to understand real pain points before building more core features. Drop your wishlist in the comments or open a GitHub issue.
Plugin developers — If you’re comfortable with Python (and optionally Vue), building a Helm plugin is a great contained project. I’m happy to pair on architecture, review PRs, and help get plugins into the marketplace. You don’t need to know the full codebase — just the plugin API.
Testers — Spin it up, break things, tell me what’s confusing. Beta feedback is the most valuable thing right now.
Corp / alliance admins — If you’re already running corp tooling and want to evaluate whether Helm fits, reach out. I’m interested in real deployment feedback.
Get involved
Discord | Helm_Develop |
If you have questions, ideas, or just want to talk EVE tooling, any of the above works. Discord is fastest for back-and-forth conversation; GitHub is better for concrete feature requests and bug reports.
Fly safe o7