Forem: Hoang Le

🚀 Calling Laravel Developers — Let’s Build a Clean, Extensible ERP (and AI Agents)

Hoang Le — Fri, 06 Feb 2026 20:18:21 +0000

🚀 Calling Laravel Developers — Let’s Build a Clean, Extensible ERP (and AI Agents)

If you’re a Laravel developer who enjoys:

Clean Architecture

Domain-Driven Design (DDD)

Extension-based systems

Writing code that stays clean years later

Then LiteERP might be something you’ll enjoy working on.

🏗️ Why LiteERP is different

LiteERP is an open-source ERP platform built with a very clear rule:

The core stays small and stable.
All complexity lives in extensions.

No massive core overrides.
No “just hack it here” solutions.

The architecture is built on:

Laravel 12

Clean Architecture & DDD

Domain Events

Clear domain boundaries

Very low framework coupling

You can read the core and actually understand it.

🎨 Hybrid Frontend (React + Blade)

One of LiteERP’s strengths is its hybrid frontend architecture.

As a Laravel developer, you can:

Build simple admin screens using Blade

Build rich dashboards using React

Mix both — per extension, not per project

No forced SPA rewrite.
No unnecessary complexity.

Each extension chooses the right UI for its job.

🧩 Extensions are first-class citizens

Everything meaningful lives in Extensions:

HRM

Debt management

SMTP

Reporting & analytics

(Soon) AI Agent Extensions

Extensions can:

Hook into domain events

Expose APIs

Add UI (Blade or React)

Be developed, replaced, or removed safely

This makes LiteERP a platform, not a monolith.

🤖 AI Agent Extensions — built the right way

We’re actively designing AI Agent Extensions that:

Live completely outside the core

Subscribe to domain events & APIs

Provide insights, recommendations, and explanations

Always keep humans in the loop

If you’re interested in:

Practical AI (not buzzwords)

Clean boundaries between domain logic and AI

Self-hosted or external AI providers

We’d love to build this together.

🌱 Open Source & Community-driven

LiteERP is fully open-source and community-driven.
We’re looking for developers who want to:

Contribute code

Design extension standards

Build AI agent examples

Shape a long-term ERP platform

You don’t need to be an ERP expert.
If you understand Laravel and clean design, you’re welcome.

👉 GitHub: https://github.com/liteerp-oss/liteerp

⭐ If the architecture resonates with you, a star means a lot
💬 Issues, PRs, and discussions are always open

Let’s build something clean, extensible, and future-proof — together.

Laravel

OpenSource

SoftwareArchitecture

DDD

AI

ERP

CALLING LARAVEL DEVELOPERS

Hoang Le — Fri, 06 Feb 2026 19:33:26 +0000

🚀 Calling Laravel Developers to build an open-source ERP platform together

If you’re a Laravel developer and you’ve ever thought:

“I wish there was a clean, lightweight, extensible ERP platform where I can build features without fighting the core…”

Then LiteERP is being built exactly with that mindset.

💡 What is LiteERP?

An open-source ERP platform built on Laravel

A lightweight and focused core

All features are developed as Extensions

You can add functionality without modifying the core

🧩 Why should Laravel devs join?

🏗️ Extension-first architecture – enjoyable to work with

⚛️ Support for React modules loaded from Extensions

🧼 Clean and actively refactored codebase

🧠 Real-world problems to solve: HRM, workflows, permissions, business logic

🤝 Who are we looking for?

Laravel developers who care about clean architecture

Developers who want to build real products, not demos

Contributors interested in meaningful open-source work

Anyone curious about building a proper ERP on Laravel

🌱 How can you contribute?

Build new Extensions

Review architecture and code

Help define Extension standards

Shape the roadmap of a Laravel-based ERP platform

👉 If you want to build an ERP platform on Laravel together, start here:

🔗 GitHub:
https://github.com/liteerp-oss/liteerp

Great platforms are not built by individuals,
but by communities who understand what they’re building.

Laravel #LaravelDeveloper #OpenSource #ERP #PHP

SoftwareArchitecture #BuildInPublic #DevCommunity #SaaS

LiteERP - Open Source

Hoang Le — Fri, 06 Feb 2026 19:31:59 +0000

🚀 LiteERP – Recent milestones in our open-source ERP journey

Over the past period, LiteERP has made significant progress in terms of architecture, developer experience, and extensibility.

🔧 A cleaner and more open architecture

✨ React ServiceProvider support
→ React modules can now be loaded directly from Extensions, without touching the core

🧩 Extension-first architecture
→ A lightweight core, with all features implemented as Extensions

🧼 Major codebase refactoring
→ Cleaner, more maintainable, and much easier for contributors to onboard

⚡ Smoother experience

Dynamic React module loading per Extension

Reduced coupling between core and features

A noticeably smoother experience for both users and developers

🧠 A growing Extension ecosystem

Some extensions already available or in progress:

🧑‍💼 HRM Extension (time attendance, leave management, HR workflows)

📧 SMTP Extension (flexible email configuration per business / tenant)

🔌 More extensions are being built following the same architectural standard

🎯 LiteERP’s vision

LiteERP is not trying to be a huge, bloated ERP system.
Our goal is:

A lightweight ERP core

Unlimited extensibility via Extensions

Allow developers to build new features without modifying the core

A practical solution for small and medium-sized businesses that can grow over time

🤝 Call for the community

If you:

Are interested in Laravel + React

Enjoy plugin / extension-based architectures

Or want to contribute to a clean, serious open-source ERP project

👉 Please take a look at the repository, share your feedback, or simply give LiteERP a ⭐ to support the project.

🔗 GitHub:
https://github.com/liteerp-oss/liteerp

opensource #ERP #Laravel #React #SaaS #Startup #SoftwareArchitecture

Call for Laravel Developers

Hoang Le — Sun, 01 Feb 2026 14:47:23 +0000

I’m building an open-source ERP project called LiteERP.

Not another “all-in-one” ERP,
but a lightweight ERP foundation built with Laravel & React,
designed around a simple idea:

👉 keep the core small,
👉 push complexity into extensions.

After working on ERP / internal systems for SMEs,
I realized most projects don’t fail because of missing features,
but because the core becomes too hard to change.

So LiteERP focuses on:
– clean architecture
– clear domain boundaries
– extension-first design
– production-oriented code (not demo-ware)

At this stage, LiteERP is NOT a ready-made ERP for businesses.
It’s a foundation for developers and teams who want to:
– build custom ERP solutions
– experiment with extension-based architecture
– avoid monolithic ERP complexity

I’m looking for Laravel developers who want to:
– explore the architecture
– build or experiment with extensions
– share feedback (good or bad)
– or simply star the project if the philosophy resonates

Repo:
https://github.com/liteerp-oss/liteerp

No hype, no marketing promises.
Just code, ideas, and real discussion.

If you’ve ever felt ERP systems are heavier than they need to be,
your thoughts are more than welcome.

Building a Lightweight ERP Core with Clean Architecture

Hoang Le — Tue, 06 Jan 2026 17:35:27 +0000

Most ERP systems fail SMEs not because they lack features,
but because they are too heavy, too coupled, and too expensive to maintain.

When we started building LiteERP, the goal was simple:

Can we design an ERP core that stays small, predictable, and extensible — even as the system grows?

This article shares some architectural decisions and trade-offs we made while building a lightweight ERP core using Clean Architecture.

The core problem with most ERP systems

From our experience, traditional ERP systems usually suffer from:

Business logic tightly coupled to frameworks

Plugins that directly modify core behavior

Growing dependency graphs that are hard to reason about

High infrastructure requirements for small teams

The result:
👉 SMEs pay enterprise-level complexity for simple workflows.

We wanted a different outcome.

Clean Architecture as a constraint, not a buzzword

Clean Architecture is often misunderstood as “just more layers”.

In LiteERP, it is treated as a hard constraint:

Domain does not know Infrastructure

Core business rules do not depend on frameworks

Modules communicate through explicit contracts

Side effects are pushed to the edge

This constraint forces discipline, but it gives us something very valuable:

The ability to change implementation details without breaking business logic.

Designing an ERP core that loads only what it needs

One key rule we adopted early:

The ERP core must not load modules it does not need.

Instead of auto-loading everything, LiteERP:

Resolves modules based on explicit support declarations

Loads only the hooks required for the current request

Avoids global service registration for unused modules

This drastically reduces:

Memory usage

Boot time

Cognitive overhead when debugging

For SMEs, this means:

Lower server costs

Predictable performance

Easier scaling decisions

Extension system: hooks, not plugins

Most ERP plugins work like this:

Override core classes

Inject logic everywhere

Break silently after updates

We avoided that entirely.

LiteERP uses a hook-based extension system:

Extensions declare what they support

Hooks are executed at specific lifecycle phases

Core rules remain non-negotiable

This gives extension developers freedom without compromising system integrity.

In practice:

Core stays stable

Extensions remain optional

Updates don’t become a nightmare

Why we avoided “feature-first” development

One temptation in ERP development is adding features early to appear “complete”.

We resisted that.

Instead, we focused on:

Correct boundaries

Clear ownership of data

Strong domain events

Full business activity logs

Why?

Because:

Features can be added later.
Broken architecture compounds forever.

Trade-offs we accepted

This approach is not free.

We knowingly accepted:

Slower early feature delivery

More upfront design work

Stricter rules for contributors

But in return, we gained:

Long-term maintainability

Easier onboarding for developers

A system that scales in complexity, not chaos

Final thoughts

LiteERP is not trying to compete with enterprise ERP systems.

It is designed for:

Small and medium businesses

Teams that value clarity over complexity

Developers who care about architecture

If you believe ERP systems can be lighter, cleaner, and more honest,
you might find this project interesting.

The project is open-source and currently preparing for Beta:
👉 https://github.com/liteerp-oss/liteerp

opensource #erp #cleanarchitecture #laravel #softwarearchitecture

Building a Lightweight ERP Core with Clean Architecture (Lessons Learned)

Hoang Le — Tue, 06 Jan 2026 17:32:47 +0000