Plugins
Plugins are packages that extend MARCO to support new features. For example, plugins can add support for a new ledger, authentication method, or data source.
MARCO provides a set of plugins ready for use with no extra configuration. Additionally, organizations and individuals can develop custom plugins to bring new functionality to the platform.
Default plugins
MARCO provides plugins that support the following features:
Identity provider
By default, users must create an account on MARCO to use the platform. This means they have to remember one more username and password. To make signing in easier, MARCO supports custom Identity provider (IdP) plugins to authenticate users using your organization's existing authentication system.
MARCO provides a plugin for SAML 2.0 authentication.
If you would like to authenticate your users using your SAML IdP, contact us.
Cloud wallet server
A Cloud wallet server (CWS) is a MARCO plugin that manages wallet instances of a specific ledger network.
MARCO provides CWS plugins for the supported DLTs.
Explorer
An explorer is a MARCO plugin that manages how to read data from a specific ledger network.
MARCO provides explorers for the supported DLTs.
Distribution model
MARCO plugins can be distributed in three ways:
MARCO shared plugins
This is the default distribution model. MARCO hosts a set of plugins ready to be used with no extra configuration. The instances of these plugins are available and shared between users and organizations.
For a list of available plugins, see Default plugins.
MARCO dedicated plugins
MARCO can host dedicated plugin instances managed by Finboot. We recommend this model when keeping your data in a separate instance is required while reaping the benefits from a managed infrastructure.
This option is only available for plugins developed and maintained by Finboot. For a list of available plugins, see Default plugins.
If you would like to host a plugin in a dedicated instance, contact us.
On-premise plugins
MARCO lets you deploy plugins on your infrastructure and connect them to the platform. We recommend the on-premise distribution model to keep complete control of the data or if you need to host custom plugins.