Pricing

 Free — $0 / month

- Seats: up to 3

- Active objects: up to 30

- Invites: add up to 2 teammates

- Members cannot be removed on Free (re-invite is allowed)

- Trial: none

- Over-limit behavior: Read-only mode : Editing is blocked until you upgrade or reduce objects.

Team — $40 / month

- Seats: up to 10

- Active objects: up to 100

- Trial: 30 days (card required)

- Over-limit behavior: Read-only mode : Editing is blocked until you upgrade or reduce objects.

Studio — $90 / month

- Seats: up to 25

- Active objects: unlimited

- Trial: 30 days (card required)

What “Active objects” means

Active objects are objects that:

1) have a server record,

2) are not marked as Missing, and

3) have a status other than UNISSUED.

Missing objects are excluded from active object counts.

What “Missing” means

A Missing object is an object that had a server record, but can no longer be found in the current Figma file structure (e.g., deleted, replaced, or significantly changed).

Missing objects are excluded from counts and can be handled by Admin housekeeping tools.

Billing, trials, and cancellation

- Paid plans are billed monthly via Stripe (not Figma native payments).

- Team/Studio trials are 30 days and require a valid payment method to start.

- After the trial ends, the subscription converts to paid and renews monthly unless canceled before the trial ends.

- If you don’t want to be charged after the trial, cancel before the trial ends.

- Cancel anytime in the Stripe customer portal. Access remains until the end of the current billing period (or trial).

- Refunds: subscriptions are non-refundable and we do not provide prorated refunds for partial months, except where required by law or in case of billing error.

Data, security, and external connections

This plugin uses a backend service (Supabase) for authentication and cloud sync.

External services

- Supabase: authentication and cloud sync

- Stripe: billing and subscription management

Data we store (examples)

- Email address (Magic Link authentication and account identification)

- Workflow data (status, assignee, comments, history)

- Figma identifiers (file/node/object IDs) required for syncing

- Payments are processed by Stripe. We do not store full card details.

Security (high level)

- Encryption in transit (HTTPS)

- Least-privilege access for internal operations

- Access control: Supabase Row Level Security (RLS) enforces per-organization data access at the database level.

- Auth: Requests are authenticated using JWT-based sessions.

Support

- Email: support@arx.institute

- We typically respond within 1–2 business days (in most cases).

- Bug reports / feature requests: email us at support@arx.institute

  - Helpful details: Figma file link (if possible), screenshots, steps to reproduce, and the time the issue occurred.