Open-source applications and reusable modules for personal, business and enterprise software. Choose a product, then choose the web, mobile or desktop presentation that fits your users.

Software · Hosting · Services · Liberu Group · Documentation

Liberu Software is an open-source software organisation building reusable applications, frameworks, libraries, and development tools across a broad range of technologies. Our ecosystem spans PHP and Laravel, Filament, Livewire, Inertia.js, React, Vue.js, Next.js, Nuxt, React Native, Expo, Flutter, Dart, and Node.js.

We develop modular, scalable, and maintainable software for web, mobile, and backend applications. From Laravel-powered platforms and administration panels to modern JavaScript frontends, cross-platform mobile applications, APIs, and Composer packages, our projects provide developers and businesses with flexible foundations for building modern digital solutions.

Our focus is on open-source collaboration, reusable architecture, clean code, and practical development standards. We aim to make high-quality software accessible to individuals, development teams, and businesses, without locking essential capabilities behind proprietary platforms. Our projects are designed for personal and commercial use under the MIT License wherever applicable, with source code, architecture, and documentation openly available for the community to inspect, adapt, extend, and improve.

Liberu brings together technologies and expertise from across the software development ecosystem, enabling solutions that integrate seamlessly across platforms and services. Whether building enterprise applications, SaaS platforms, APIs, websites, administrative systems, or native and cross-platform mobile apps, we provide the tools, packages, and foundations to accelerate development.

Liberu is supported by commercial software development, application integration, consultancy, technical support, and hosting services. This sustainable model helps fund the continued development, maintenance, and expansion of our open-source ecosystem while keeping our projects accessible to everyone.

Start with a Boilerplate foundation for a new application, or choose a product repository from the catalogs below. Laravel hosts own domain rules and authorization. Independent web and device applications integrate through reviewed APIs.

The Dart desktop and mobile families use Flutter native hosts with Dart application code. They remain separate applications from the general Flutter mobile family, with their own platform configuration and release identities.

Choose Filament for administrative panels, or Inertia with Vue/React for Laravel-owned page routes and sessions.

Choose Nuxt with Vue or Next.js with React for independently deployed web applications and server rendering.

Choose React Native with Expo, Flutter mobile, or a separate Dart mobile/desktop application.

1. Select a repository above and read its README and AGENTS.md.
2. Use its pinned toolchain and lockfiles. Follow the initialization catalog and presentation runbooks.
3. Select reviewed domain/API modules and implement one authorized journey before expanding the application.

Existing Filament repositories retain their product implementations. The other presentation repositories are starting structures with build configuration and explicit integration boundaries; they do not claim completed workflows, device releases or feature parity. Each README links related products using the same presentation and summarizes the alternatives for that product.

These badges describe the application foundations' supported technology families. Exact resolved versions live in each repository's lockfiles: the current web/mobile starters use React 19.3, Vue 3.5, Next.js 16.4, Nuxt 4.6, Expo 58 with React Native 0.88, and Flutter 3.47 with Dart 3.13. Existing application manifests remain authoritative during upgrades.

Browse the capability module catalogs for separate package repositories across every presentation and their current rollout status.

Application templates and project skeletons use the project- prefix. Reusable module repositories use module-.

Applications compose independent modules. PHP packages use Composer, JavaScript/TypeScript libraries use npm, and Dart/Flutter packages use pub metadata. Reuse canonical owners and keep deployment, application IDs and registry package identities separate from repository names.

Start with the architecture, module guidance and contribution standards. New presentation packages remain skeletons until their contracts, consumer builds and meaningful journeys are verified. Repository creation does not publish a package to a registry.

YouTube · Facebook · Instagram

Application templates use project-; independent reusable modules use module-. Start capability packages from the matching module foundation and preserve their independent Composer, npm or pub metadata. These templates expose extension points; they do not implement product workflows.