Weave Code
Core Laravel Package
flarum/core
Flarum is free, open-source forum software built on PHP with a fast, modern frontend. It's lightweight, extensible, and designed for smooth community discussions, offering a clean default theme and a rich extension ecosystem.
Flarum is a fast, elegant open-source forum platform built on PHP with Laravel components and a Mithril.js frontend. Its lean core keeps pages snappy, while a powerful extension API lets you tailor everything from themes to permissions without touching the source.
- Blazing-fast single-page interface with minimal payload
- Highly extensible architecture for plugins and themes
- Responsive, mobile-first design out of the box
- Rich permissions and moderation tooling
- Modern REST API for integrations and apps
Frequently asked questions about Core
- Is flarum/core a Laravel package I can install with composer require into an existing Laravel app?
- No. flarum/core is standalone PHP forum software that consumes Laravel's Illuminate components (Eloquent, migrations, cache, sessions, mail, validation, and the container) while shipping its own application kernel, JSON:API layer, and Mithril.js frontend. There is no service provider to register inside an existing Laravel application; you deploy Flarum as a separate document root alongside your app. Treat it as a neighboring PHP application, not a drop-in Composer package.
- Which Laravel components does Flarum actually use?
- Flarum uses Illuminate components including Eloquent for models, database migrations for schema, cache, sessions, mail, validation, and the service container. It does not use Laravel's HTTP kernel, routing, or Blade as the main application layer. That means Laravel developers can read models and write migrations on day one, but the surrounding application lifecycle is Flarum's own.
- How should I integrate Flarum with an existing Laravel application?
- The recommended posture is to deploy Flarum standalone, for example at community.example.com, and bridge identity through an OAuth2/OIDC or custom auth driver. You can syndicate content into your Laravel app through Flarum's JSON:API. A headless content-source pattern, pulling threads and posts via /api for SEO pages, digests, or unified search, is also viable and low effort. Avoid embedding Flarum's kernel inside a Laravel app or trying to share sessions and middleware in-process.
- Can Flarum use my Laravel app's authentication for single sign-on?
- Yes, through Flarum's auth extension ecosystem (OAuth2, SAML, LDAP) or a custom auth driver, so SSO is generally a configuration plus one class rather than a fork. You should decide whether the identity bridge needs to be bidirectional, including profile sync and ban propagation. Flarum is not automatically wired to Laravel's guards or session; you bridge at the protocol level.
- Can I pull Flarum forum threads and posts into Laravel using the JSON:API?
- Yes. Flarum's JSON:API is stable, documented, token-authenticated, and supports filters, includes, pagination, and sparse fieldsets, which is enough to build a Laravel-side sync job or internal read model. That lets you create SEO pages, digests, or unified search without touching Flarum internals. It is the cleanest integration lever between the two applications.
- What frontend stack does Flarum use, and can my Blade or Vue team work on it?
- Flarum's frontend is a Mithril.js single-page application written in TypeScript, not Blade, Livewire, Vue, or React. A team fluent in those Laravel-adjacent tools cannot directly reuse that knowledge; custom UI work is a genuine ramp-up. Plan for someone who will own Mithril and TypeScript frontend work, or expect every UI change to become a contractor engagement.
- How are Flarum extensions installed, and are they Composer packages?
- Flarum extensions are Composer packages that declare type: flarum-extension and bootstrap through an extend.php file, which is a clean, declarative extension contract. Bundled first-party extensions are generally safe, but the community long tail has variable maintenance quality. Adopting a third-party extension means adopting an unowned dependency, so identify non-negotiables such as search backends, spam filtering, or payments and confirm who maintains each.
- What are the risks of upgrading Flarum major versions?
- The 2.x line carries breaking changes to the extension API and frontend toolchain, so any extension you depend on can become a migration blocker. That makes major-version churn the dominant lifecycle cost to budget for. Before committing, inventory your required extensions and verify each has a maintained path to the next major release.
- Is Flarum a good alternative to Discourse, NodeBB, XenForo, or Vanilla?
- Flarum is fast, mobile-first, open-source PHP forum software with a clean modern interface and a rich extension ecosystem. The forum category is mature and crowded, so the marginal value over an incumbent is usually community UX and PHP-stack coherence rather than unique capability. Justify adoption on those grounds, and consider an embedded comment service instead if the real requirement is discussion inside your product rather than a standalone forum.
- How reliable is Flarum's release cadence and maintenance?
- Bundled first-party extensions are maintained with core, but community extensions vary. One data-integrity flag: a reported last-release timestamp of 2026-10-14 is anomalous and future-dated, so treat the freshness signal as unreliable until you verify directly against the GitHub releases feed. Confirm current release activity and extension compatibility before committing.
Weaver
How can I help you explore Laravel packages today?