Plugins · five first-party

Capabilities you copy in

A Rocketflare plugin is a git repository copied into your application — never an npm package. Its code lands as ordinary source, renamed into your own vocabulary on the way in, and deleting its folders takes it back out. Here is what is published today, what each one adds, and the one command that installs it. How the seam works →

5 plugins

  • Installed by default

    Analytics

    Dashboards, cubes, fact tables and the drizzle-cube query API — everything that used to be part of the kit, now a repository of its own.

    • 3.4.2
    • kit ≥ 0.13.0
    • 4 skills
  • Add it when you need it

    Web knowledge

    Lets agents and chat search the public web and read pages, on each organisation’s own search key — and only for the organisations that turn it on.

    • 3.4.2
    • kit ≥ 0.9.0
  • Add it when you need it

    Connectors

    Connects an organisation’s own Microsoft 365 to your app: an admin grants consent once, and its directory and calendars sync in. It holds the rows, routes and schedules; a provider plugin (today, m365) does the talking.

    • 3.4.2
    • kit ≥ 0.13.0
    • 1 skill
  • Add it when you need it

    Microsoft 365

    Microsoft 365 as a provider for the connectors plugin, which it requires — install connectors first. One multi-tenant Entra app for your whole deployment; each customer’s admin consents to it once.

    • 3.4.2
    • kit ≥ 0.12.0
    • needs connectors
  • Ships in the kit

    Example feature

    The reference plugin: a notes list that touches every slot the seam has, so you can read one small thing instead of a large one. It ships in the kit and exists to be deleted.

    • 0.1.0
    • kit ≥ 0.8.0
    • 1 skill

Writing one of your own

A plugin is a repository with a manifest, three directories and four entry files. The kit ships the reference one in its own tree so you can read a small, complete example before writing anything: a table, a gated route, a job, an agent tool, a page, two commands and its own tests. Point pnpm plugin add at a local path and it installs from there, which is the authoring loop.

Read the concept Get the kit running