Plugins

Developer portal

Q: Can I sell inside my plugin?

Yes, with top-ups: declare billing.items in definePlugin and price them in the portal. See the Plugin SDK.

The developer portal (/developer) is where teams build, publish and sell plugins for Beamvia workspaces. Beamvia reviews every developer and every build before it reaches workspaces. You write plugins with the Plugin SDK; this page covers everything around the code: your team, keys, uploads, review, releases, prices and revenue.

The path

Apply to publish plugins.
Build your plugin with the SDK and test it in your test workspaces.
Upload a build (or bun run publish); it goes to review.
Release the approved build; installs move after a cooldown.
Write the store page and set a price; both are reviewed.
Watch installs, ratings, issues and revenue.

1. Apply

Open Developer → Apply to publish plugins with:

Name of your team or company.
Slug: how other developers find you to transfer plugins.
Scope: every plugin key starts with it (@acme/shipping). It can't change later. Some scopes are reserved (@beamvia, @official, @whatsapp…).

The application shows Waiting for review, then Approved or Rejected. An owner accepts the developer agreement, and again whenever it changes (The developer agreement changed) before the next upload.

2. Team and roles

Role	Can
Owner	Everything, including the developer's own settings
Admin	Submit and publish builds, manage plugins, members and keys, see revenue
Developer	Submit builds and view the developer

Publishing a build, managing members and keys and changing the developer need a code we email you (valid 10 minutes). Members › invite people by their Beamvia account; they join right away and take a seat.

3. Keys

API keys submit builds from your terminal or CI (bun run publish with BEAMVIA_DEVELOPER_KEY). A key can only submit builds; name it after where it runs so you know which one to revoke.

4. Test workspaces

Settings › Test workspaces: up to 3 workspaces owned by your members can run any build of your plugins, even before review. Never billed, never listed. The plugin's page in such a workspace offers Test version.

5. Upload a build

In the plugin package run bun run build: it writes dist/package.zip (bundles and source maps, so the review can read your code, plus your listing/ store page).
Upload a build in the portal, or run bun run publish.
The version comes from the manifest and must be newer than every release. Add a changelog (workspaces see it when they update) and notes (only the reviewer sees them).

The key in the manifest creates the plugin on its first upload. The build shows in the Review queue: Waiting, Approved, Rejected or Withdrawn. A rejected build can be fixed and uploaded again with the same version.

6. Release

An approved build waits until you Release it (owners and admins).

Cooldown: installs move to the new version after 60 minutes (6 hours for plugins with 100+ installs and for a new maintainer's first build). Halt stops it during the cooldown or after: no more installs move to it, and those already on it stay until a newer release or a rollback.
Rollback to an earlier reviewed build moves installs back at once (no cooldown).
A version that asks for more than the one workspaces run (new hosts, abilities, required settings) waits for each workspace to Accept and update.
The Release log shows each release, when installs moved, halts, rollbacks and forced releases.

7. Store page and prices

Store page: tagline, description, highlights, cover and gallery, setup steps, FAQ, categories, tags, links and SEO. See Plugin store › Write a great store page.
Prices: a one-time workspace license in the site currency (IDR). Leave it at 0 to keep the plugin free; workspaces that install it while free own it too. Paid plugins need a privacy policy and a support email.
Top-ups: items your plugin sells inside (credits, packs), declared in the build's billing.items, priced in the portal.

Beamvia reviews every store page and price change.

8. Revenue

Beamvia keeps a platform commission of every paid sale (30% by default; a developer may have its own rate). Revenue shows sales and your share.
A sale becomes payable after a 14-day refund window. A refunded sale takes the license back.

Grow and maintain

Tab	What's there
Last 30 days	Store views, installs, uninstalls (with reasons), conversion, where visits came from
Ratings	Workspaces' ratings and comments
Issues	Workspace reports and Beamvia's security issues, with a deadline by severity: Critical 3 days, High 14, Medium 30
Feedback	Uninstall reasons

Beamvia can add a strike to a plugin (for example a missed security deadline); strikes count toward suspending the developer (Suspended by Beamvia: read-only).

Settings

Security contact: where Beamvia sends security issues (else your owners and admins).
Verified developer: prove you own your domain with a DNS TXT record. The store badge also needs 6 months without strikes.

Danger zone

Transfer a plugin to another developer by their slug. They confirm first, then Beamvia approves; every workspace is asked to accept the new maintainer.
Unlist: workspaces that installed it keep it; new ones can't find it.