Manifest-first
Identity, capabilities, events, configuration, dashboard components, and runtime services are described in predictable files.
Pre-release · Open standard · Local runtime
Griffino
An open standard and local runtime for plugins that find each other by capability, compose safely, and stay on the user's own machine.
What Griffino is
Plugins connect by capability, not by hard-coded dependency.
A plugin only needs to describe what it can provide and what it needs. Griffino uses that contract to discover compatible providers, route messages, and keep local workflows understandable as they grow.
The standard
Portable plugin contracts for authors and runtimes.
Capability routing
Plugins provide and consume typed capabilities. Providers can be swapped without forcing every consumer to know the implementation.
Schema-backed
Standard interfaces and JSON schemas give the ecosystem a shared contract that SDKs and tooling can validate.
Reference runtime
A local daemon that orchestrates plugins, messages, state, and APIs.
The current implementation launches plugins as Docker containers, assigns isolated RabbitMQ namespaces, manages Redis-backed state, exposes a local API, and includes a web console for day-to-day operation.
Plugin isolation
Containerized plugins with predictable lifecycle management.
Capability routing
Local message routes between compatible providers and consumers.
Operation surface
API, scheduler, state, health, metrics, and web console.
Default-local security
The API binds to localhost by default, supports authentication, and encrypts sensitive credentials at rest.
Observable by design
Prometheus metrics, OpenTelemetry traces, plugin health, and scheduler state are part of the operating model.
Blueprint-ready
Triggers, scheduled work, and capability-compatible ports give plugins a path into composable local workflows.
Project repositories
Core runtime, SDKs, schemas, and plugin ecosystem entry points.
GriffinGuard/Griffino
Reference implementation, daemon, CLI, routing, API, scheduler, and container orchestration.
Griffino-WebUIEmbedded web console for operating Griffino from the browser.
Griffino-PluginsOfficial plugin center repository and reviewed image allowlist.
Griffino-Plugins-SubmitSubmission path for plugin authors who want to enter the official center.
Griffino-SchemasJSON schemas and versioned interface contracts that define the standard.
Griffino-GoGo SDK for implementing provider and consumer plugins.
Griffino-PythonPython SDK for building Griffino-compatible plugins.