Skip to content

Framework for Organizational Resilience: Global IT and Future Trends. FORGIFT, obrt za informacijske usluge, vl. Karlo Njegovan. Zadar, Hrvatska. Web development, backend systems, and operational software. Contact: forgift.hr@gmail.com.

PRJ-03 / PLUGIN PLATFORMIN DEVELOPMENT

FORGE

A self-hosted Symfony platform for composing small plugin-based tools—dashboard widgets today, growing into commands, data tools, automations, and controlled integrations.

PluginsDashboardsSelf-hosted
01 / OVERVIEW

One platform, many small tools.

FORGE is built around a capability-oriented plugin model. Plugins start as dashboard widgets and can grow into commands, data tools, automations, and controlled integrations without needing a new platform each time.

It is a runnable Symfony application with MariaDB-backed users, secure local authentication, workspace memberships, and both personal and shared dashboards—built to support plugin authoring from day one rather than bolted on later.

02 / CAPABILITIES

The baseline already in place.

01

Dashboard widget windows

Draggable, resizable floating widgets with Windows-style edge and corner snapping, persistent z-order, docking, and minimize/maximize state.

02

Plugin authoring studio

A live manifest and starter-code studio for building new plugins from inside the platform itself.

03

Workspace plugin control

A dedicated control plane for managing which plugins a workspace can install, configure, and run.

04

Per-instance configuration

Schema-validated configuration for each widget instance, so the same plugin can be tuned differently per dashboard.

05

Sharing and permissions

Personal dashboards plus named viewer/editor sharing, revocable public read-only links, and persisted permission grants.

06

Predefined catalog

Administrator review turns a reviewed private plugin identity into a published, workspace-wide catalog entry.

03 / PLUGIN LIFECYCLE

From private draft to running widget.

01

Author

Build a plugin privately from the in-platform starter-code studio.

02

Review

An administrator reviews and publishes the plugin identity into the predefined catalog.

03

Install

Workspace members enable the plugin from the plugin control plane.

04

Run

The plugin runs as an isolated, draggable dashboard widget with its own scoped configuration.

04 / TECH STACK

A self-hosted Symfony foundation.

Backend
PHP 8.2+ / Symfony 7.4 LTS
Frontend
Twig / AssetMapper / Stimulus
Database
MariaDB / Doctrine ORM & Migrations
Security
Symfony Security, CSRF protection, login throttling
05 / ISOLATION

Plugin code, sandboxed by design.

Third-party plugin code runs isolated from the host dashboard through browser-plugin execution boundaries, so a misbehaving plugin can't reach into the platform or the page around it.

06 / REFERENCE PLUGIN

A working example, not just a spec.

com.forge.example.url-monitor ships as a working plugin, with status and history widgets that consume a host-supplied forge.data snapshot instead of making direct browser network calls.

07 / ENABLED PLUGIN PAGES

Every plugin gets a real page.

Each enabled plugin is reachable at its own /plugin/{plugin-id}/ route, linked from the main navigation—not just a widget buried on a dashboard.

08 / DESIGNED FOR

Built for people who'd rather host one platform than ten scripts.

  • Self-hosters who want one platform for small internal tools instead of one-off scripts
  • Developers who want to ship a widget quickly and grow it into a command or automation later
  • Teams who need workspace-level control over which plugins get installed and shared
  • Anyone who wants plugin code kept away from direct browser network access
09 / STATUS

Runnable today, still taking shape.

FORGE already runs as a full Symfony application with authentication, dashboards, and plugin authoring in place. It is backed by a full internal specification—project definition, application architecture, plugin specification, startup plan, and deployment guide—as the platform continues toward its first releasable version.

Discuss FORGE