The OpnForm Alternative That Lives Inside Your Laravel App

Standalone application versus plugin

The distinction affects daily work more than the feature checklist. With OpnForm, your team owns a separate application. It has its own deployment, environment settings, user access, and database connection.

With FilaForms, forms appear in the Filament panel your team already uses. Your existing authentication, permissions, deployment process, and database remain the operating context. A form manager does not need another login or another administration interface.

This also changes where submissions live. FilaForms stores submission data in your application's database. That makes it practical to relate a submission to the customers, teams, or records already stored there.

OpnForm stores submissions in the database used by its separate application. That works well when forms need their own boundary. It adds a data connection to plan when your main Laravel application needs those submissions.

FilaForms ships a visual drag-and-drop builder, more than 25 field types, conditional logic, multi-step forms, email notifications, a submission dashboard, and analytics. The field count matters once a contact form grows into a workflow with uploads, dates, and branching.

Read the Laravel form builder features to see the available building blocks. The useful question is not whether both products can publish forms. The useful question is whether forms belong inside your existing product or beside it.

What a second application actually costs

The comparison table lists the differences. The operational weight behind them is what decides most migrations.

A standalone form application needs its own deployment pipeline, environment variables, TLS certificate, backup schedule, and upgrade window. It needs its own user accounts unless you wire up single sign-on. Every one of those is small on its own. Together they are a second system your team is on call for.

A plugin inherits all of it. The deploy that ships your application ships your forms. The backup that protects your database protects your submissions. The permissions that already govern your Filament panel govern who can edit a form.

The trade runs the other way when forms must outlive or stand apart from one product. If three applications need the same form system, running one form service beside them is cleaner than installing a plugin three times. OpnForm suits that shape, and its hosted option removes the operations question entirely.

There is also a data question worth settling early. FilaForms stores submissions in your application database, so a submission can reference a customer row with a foreign key. OpnForm keeps submissions in its own database, so joining them to your product data means moving data between systems on a schedule you maintain.

Register FilaForms in an existing panel

Installation belongs in the Filament panel provider. The following Laravel 12 and Filament 4 provider registers the plugin in an existing application.

<?php

declare(strict_types=1);

namespace App\Providers\Filament;

use FilaForms\Core\FilaFormsPlugin;
use Filament\Panel;
use Filament\PanelProvider;

final class AdminPanelProvider extends PanelProvider
{
    public function panel(Panel $panel): Panel
    {
        return $panel
            ->default()
            ->id('admin')
            ->path('admin')
            ->login()
            ->plugin(FilaFormsPlugin::make());
    }
}

This registration keeps the form builder where your administrators already work. It also makes FilaForms a poor fit for a non-technical group that needs a hosted form link in five minutes. FilaForms requires an existing Laravel and Filament application. It has no cloud version.

If that limitation describes your situation, OpnForm's hosted option is the faster path. It lets you start with a form service before you operate a Laravel application. You can revisit an in-application plugin once your product and administration panel exist.

Check the licence before you assume

OpnForm is an active PHP project: 3,656 GitHub stars and commits landing the day this page was last checked, on 2 September 2026. That maturity is a genuine argument for it.

The detail worth reading yourself is licensing. GitHub reports OpnForm's licence as "Other" rather than a standard OSI identifier, because the repository ships a custom LICENSE file rather than a blanket open-source grant. Read that file before you plan a modified self-hosted deployment. FilaForms takes the opposite approach and makes no open-source claim at all: it is a commercial plugin with a one-time licence per plan.

When FilaForms is the better choice

Choose FilaForms when your application already has Laravel, Filament, authenticated staff, and a database. It suits a team that wants customer data and form submissions in one application boundary. It also suits teams that want form management beside the records their staff already administer.

Start with the FilaForms homepage if you need to confirm that model. Review your current panel provider before installing anything. The implementation should use the panel and authentication rules that already protect the rest of your application.

Choose OpnForm when the form service should stay independent from your product. Its standalone model can be simpler for a separate marketing site, a new project without Laravel, or a team that wants the hosted option. That is a valid trade-off, not a feature gap.