Pricing

Pro is a single-seat plan for one power user running their own data ops: unlimited canvas uploads, the full AI cap, the script runner, and reusable slot-canvas templates. You’re the only one in your workspace; the settings you configure govern your own use. Self-serve, $99/month, billed monthly.

Team is what you upgrade to when other people in your org also need to use Org Loom and you need oversight of what they’re doing. It’s not “Pro plus extra features.” It’s governance and audit over multiple users acting against your Salesforce orgs. You get multi-member workspaces with admin and member roles, a workspace-wide activity log so admins can see every member’s actions, a production-org approval gate so risky writes pause for admin review, and admin-controlled policy (script runner, AI tools, Salesforce writes, and exports) that applies workspace-wide instead of per-user. Team also includes priority email support and one admin onboarding session to help configure the shared workspace. Team starts at $399/month with three users included. Additional active users are $49/month each; Viewer and Contributor recipients are free. See the next question for details.

$399 per month including three users. Each additional active user is $49 per month. One seat covers one Salesforce identity regardless of how many Salesforce orgs they connect. Viewer and Contributor recipients do not require a paid seat.

Larger teams. If you’re scoping a 10+ seat rollout, email us before you sign up. We have volume discounts and we’d rather work them in up front than process a credit later. Most teams hear back within a business day.

Annual billing gives you two months free versus monthly (see Do you offer an annual discount? below).

Yes. Upgrades take effect immediately and are prorated; downgrades apply at the start of the next billing cycle so you don’t lose paid features mid-month.

One click of Upload = one upload, no matter how many records went up. Failed uploads (validation rule rejected, payload too big, all rows errored) don’t count. Otherwise debugging a broken record would burn through your monthly allowance. Caps reset on the 1st of each calendar month.

The Generate-with-AI flow returns a clear “you’ve reached your monthly token cap” message. You have three options: wait for the cap to reset on the 1st, buy AI add-on credits to keep going this month, or upgrade to Pro for unlimited generations. Existing records on the canvas aren’t affected.

A top-up that extends your monthly AI cap without changing plans. One credit equals one Anthropic token (the same unit your plan’s cap is measured in), so generating against credits feels identical to generating against your monthly allowance. Credits don’t expire and roll over month to month. Available on every plan. A workspace admin can buy a top-up anytime from the Billing tab in workspace settings.

Org Loom has two AI surfaces and they bill differently.

In-app AI generation. The Generate-with-AI button on the canvas, AI-on-canvas-data suggestions, and other features we drive from inside Org Loom. These calls run through our Anthropic relationship and consume against your plan’s monthly token cap (500,000 on Pro, 500,000 per seat on Team). One bill, included in your subscription.

MCP tool calls. When you connect Claude desktop, Claude.ai, Cursor, ChatGPT Enterprise, or any other MCP-aware AI client to your Org Loom workspace, the AI runtime lives in that client. Those tokens are billed by Anthropic (or whoever runs the AI) directly to whichever account pays for that AI client. Org Loom is just the tool surface. We never see those tokens and they don’t count against your Org Loom AI cap, so heavy MCP use never increases your Org Loom bill. MCP token issuance is a paid feature, available on Pro and Team.

There are two separate sign-ins, and it helps to keep them apart. Org Loom account sign-in uses Google, Microsoft, or an email magic link today; SAML/OIDC SSO for enterprise is on the roadmap. Connecting a Salesforce org is separate: it runs through Salesforce OAuth, so your org’s own IdP (Okta, Azure AD, Google Workspace, etc.) is enforced at connect time, and we never store Salesforce credentials or refresh tokens. Because every data action requires a live Salesforce connection as an active user in that org, removing someone from Salesforce immediately cuts off their access to your data and saved canvases - even if they still have an Org Loom login.

Salesforce data transits through Org Loom servers (the browser doesn’t talk to Salesforce directly), but we don’t persist row data. The request/response cycle returns it to your canvas and that’s it. Activity History records metadata (record IDs, counts, errors) but never field values.

We also don’t store your Salesforce credentials. Org Loom doesn’t request the refresh_token / offline_access OAuth scopes, so no long-lived credential is ever issued to us. A short-lived access token lives in your encrypted session for the duration of your visit and is wiped on sign-out; mid-session expiry is handled by a silent OAuth renewal against your existing Salesforce session. We cannot act against your org when you’re not signed in.

Canvases you save with Save canvas state to Salesforce are stored as files in your Salesforce org, not on Org Loom infrastructure. Local-only saves live in your browser’s storage.

The Recall ledger (which records were inserted in each upload so you can later undo a batch) is also stored as a file in your Salesforce org, owned by your SF user and governed by your SF Files retention policy. Org Loom doesn’t hold the inserted-record IDs, custom object/field API names, or parent/child associations from your uploads.

AI generation only ever receives object and field schema (names, types, picklist values). Your record values never enter the AI prompt.

Yes - pick Annual at the top of this page. Annual billing on Pro and Team gives you two months free (you pay for 10 months, get 12): Pro is $990/year instead of $1,188, and Team is $3,990/year instead of $4,788. Additional Team users are $490/year instead of $588. Annual seats can be added or removed at renewal.

Yes. The canvas core behind orgloom.com is published under the PolyForm Internal Use License on GitHub. Your security team can read it before you connect a Salesforce org. The license permits running the code on your own infrastructure for your company’s own internal use: not for providing services to third parties, not for hosting it as a managed service, not for redistribution. Self-hosted deployments are unsupported: there’s no install guide promises, no Docker image SKU, no managed self-host tier, and no help in issues. The product we build, run, monitor, and support is orgloom.com.

We don’t pursue custom enterprise contracts. If Pro or Team don’t fit, the source is right there for your security team to read.