Flarum

Self-hosted discussion forum and community workspace.

4 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    VM image; Docker / Compose

  2. Operated by

    Your team

    Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.

Deployment boundaries by provider
  • Hostinger: Customer VPS account · Customer-operated

    An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.

    Hostinger ↗ · Source checked 2026-11-19

  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Microsoft Marketplace ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodVM image; Docker / Compose
InfrastructureServers / containers
Flarum PHP application, database, attachments and extension configuration. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelOpen Source / Open Core
MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseMIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

7 of 12 fields researched (58%) · 6 documented · 1 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
AvailableEvidence and scope for Marketplace delivery

The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance.

Flarum selected Azure public offer · Source ↗ · Offer cloudimg1647283583153.flarum-ubuntu-24-04 ↗ — cloudimg; Virtual machine · Reviewed 2026-11-19

Documented · Editor reviewed.

Cloud commitment eligibility
Not eligibleEvidence and scope for Cloud commitment eligibility

The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement.

cloudimg1647283583153.flarum-ubuntu-24-04 public offer, reviewed 2026-11-19 · Source ↗ · Reviewed 2026-11-19

Explicitly unsupported · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

The published fof/oauth 2.0.2 extension requires flarum/core ^2.0.0 and provides external OAuth-provider login. Use the 2.x-compatible release; the older master/1.x metadata requiring ^1.8.1 must not be used for a Flarum 2 deployment. Configure and test the chosen provider and extension permissions separately.

Third-party FriendsOfFlarum OAuth 2.0.2 for Flarum 2.x; not core-native SAML · Source ↗ · Published maintainer package/version metadata ↗ · Matching release provider documentation ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The official 2.x guide provides archive and Composer-based application installation, database configuration and update instructions. It requires compatible PHP/database extensions and maintenance access; an extension or marketplace image built for 1.x is not automatically compatible with 2.x.

Upstream Flarum 2.x application installation · Deployment artifact ↗ (Current 2.x release/archive or Composer application; pin core and extension versions) · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

The 2.x installation guide specifies PHP 8.3+, web-server and supported database requirements, but no quantitative production CPU/RAM/storage minimum was established. Confirm database, extension, search and active-user requirements for the intended deployment.

Current 2.x software prerequisites; numeric production host floor remains open · Source ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Flarum; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

Reviewed upstream v1.8.21 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.

Flarum upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (5 not researched)
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

The maintained 1.8 stable series and 2.x preview series are separate. Extensions may have different licences and upgrade compatibility.

Community & maintenance

The reviewed upstream contributor history includes tobyzerner, franzliedke, flarum-bot, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Category fit

Collaboration
Self-hosted discussion forum and community workspace.

Compare within Collaboration

  • 3CX Self-HostedCommercial business communications and PBX platform installed into the customer's public-cloud account.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Commercial Only
  • Apache AnswerSelf-hosted community questions, answers and knowledge content.
    • AWS
    • DigitalOcean
    • Railway
    • Linode
    • Vultr
    • Hostinger
    • LumaDock
    Customer-operated · Open Source / Open Core
  • BigBlueButtonSelf-hosted conferencing and virtual classroom platform.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    • Hetzner
    • Scaleway
    Customer-operated · Open Source / Open Core
  • BookStack Self-HostedSelf-hosted wiki and documentation organized into books, chapters and pages.
    • AWS
    • DigitalOcean
    • Linode
    • Vultr
    • Hostinger
    • LumaDock
    Customer-operated · Open Source / Open Core
  • Campfire (ONCE)Self-hosted group chat and team conversation application.
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Collabora Online (CODE)Community office editing server for integration with a document platform.
    • AWS
    • DigitalOcean
    • Hetzner
    • Linode
    • Vultr
    • Hostinger
    • LumaDock
    Customer-operated · Open Source / Open Core
  • Confluence Data CenterCommercial self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • DiscourseSelf-hosted discussion and community platform for workplace collaboration and customer support communities.
    • AWS
    • Google Cloud
    • DigitalOcean
    • Hetzner
    • Linode
    • Vultr
    Customer-operated · Open Source / Open Core

Showing 8 of 25 other listings in Collaboration. These products address related workflows; read their category-fit notes before comparing scope. See all of Collaboration →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Hostinger ↗ · Hostinger

      Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Flarum PHP application, database, attachments and extension configuration. The maintained 1.8 stable series and 2.x preview series are separate. Extensions may have different licences and upgrade compatibility.

    • Microsoft Marketplace ↗ · Azure

      Marketplace offer · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Flarum PHP application, database, attachments and extension configuration. The maintained 1.8 stable series and 2.x preview series are separate. Extensions may have different licences and upgrade compatibility.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory