Digital Toolkit


Plugin Framework > Architecture > Hosting
Good to Know
Plugins are hosted in your own public-facing web server and displayed to the user in Banno’s UI when necessary.

System diagram

Banno Mobile and Online include a Dashboard UI which summarizes useful information for the user using a card metaphor. The user’s Dashboard can be configured to display your custom plugins using the same card metaphor. The primary difference between Banno’s built-in cards and your custom plugins is where the content is hosted.

  • Banno’s built-in cards: for features which are part of Banno itself, the content is hosted by Banno and displayed to the user when necessary.
  • Plugins: the content is hosted by your public-facing web server and displayed to the user when necessary.

The system diagram illustrates this relationship.


Banno will use the plugin configuration to determine which web service it will ask to respond with web content for the plugin’s UI when a plugin is loaded by the Dashboard.


Plugins that want authenticated information about the user will need to handle an authentication request and exchange with Banno. Your web server must be capable of handling this type of request if you want to provide custom information based on the specific logged in user. See the Authentication topic for more details.

Responsive design

Plugins should return web content that is designed to be responsive and adapt to a variety of screen sizes to accommodate a great user experience for both Banno Mobile and Banno Online users.

Have a Question?
Have a how-to question? Seeing a weird error? Get help on StackOverflow.
Register for the Digital Toolkit Meetup where we answer technical Q&A from the audience.
Last updated Thu Jun 22 2023