AEGIS v1 is archived. Here is what replaces it

Description and use

AEGIS v1 is archived; its code remains public but will not be maintained. A new, modular AEGIS v2 is under development, addressing deployment, database, and modularity issues.

Problem

AEGIS v1 was a monolithic system that combined tasks, email, money, research, and home‑automation alerts into a single deployment, database, and codebase, making maintenance risky and preventing modular reuse.

Outcome

AEGIS v1 is archived; its code remains available but will not be maintained. A new, modular AEGIS v2 is under development, addressing deployment, database, and modularity issues.

Workflow

• 1. Shut down AEGIS v1 and archive the GitHub repository.
• 2. Keep the source code public under MIT license for reference.
• 3. Announce that AEGIS v2 will be developed as a non‑open‑source project.
• 4. Explain the reasons for the migration: monolithic deployment, shared database, lack of modularity.
• 5. Provide a link to the full post for detailed implementation plans.

Evidence

I’ve shut down AEGIS v1 and archived github.com/hikmahtech/aegis. The code stays public and MIT‑licensed. You can still read it, fork it and learn from it. It just won’t get fixes, releases or answers to issues any more.

Source

AEGIS itself isn’t going away. It is being rebuilt as version 2, and version 2 is not open source.

Source

One deploy for everything. A fix to bank‑statement parsing redeployed the code that restarts services in my homelab. Every change carried the risk of every other area.

Source

One database for everything. The accounting tables and the alert tables lived side by side. Nothing stopped one area from reading or writing another’s rows, so over time some did.

Source

Nothing could leave. If someone wanted just the bookkeeping part, there was no way to give it to them. It came with my task manager, my research feeds and my infrastructure agent attached.

Source