Step 01
Publish it
Drag the exported dashboard in, or publish straight from Claude Desktop and Cowork.
Because you publish from Claude or your own browser, company data never passes through a third-party build step.
For teams building on Claude
Your team builds great dashboards in Claude. Sharing them is where it breaks down.
Publish the dashboard you built and get back a link only people at your company can open. No infra to set up. When the numbers move, publish again and the link stays the same.
Viewers sign in with your company's SSO or work email. Access follows your IdP, so it ends when someone leaves.
Company-only · live
Q4 pipeline
Updated 10:42
Pipeline$4.2M
Win rate38%
Avg cycle41d
How it works
From a finished dashboard to a company-only link
No deploys, no settings to learn. You publish, you get a link, and you send it to whoever needs it.
Step 02
Get your link
A company-only link, ready in seconds. There's no build to wait on.
One link, one address. When the data changes, publish again and everyone sees the new version at the same URL.
Step 03
Share it
Your team opens it with their existing company login. Nothing to sign up for, no new account.
Each viewer authenticates through your identity provider, so every view ties back to a real person and deprovisioning follows your IdP.
For VPs and budget owners
The analysis your team produces in Claude mostly stays on one laptop.
A good dashboard gets built, then circulated as a screenshot or a file, or not at all, because there's no safe way to put internal numbers somewhere the whole team can open them. The work exists; the reach doesn't. Artifactive gives it a company-only link, so the analysis you've already invested in actually lands with the people it was built for.
Freefor viewers, the whole org can open it
$149/moflat, on a card
No infra,deploys, or procurement to get going
Access and identity
Why a shared password usually isn't enough
Some tools gate a link with one shared password. That's fine for low-stakes content. For internal company numbers, a security team needs to know who actually viewed something and to revoke access when someone leaves. A shared password does neither.
A shared password
- One password for everyone, easy to forward outside the company
- No way to tell who opened the dashboard
- No clean way to cut access after someone leaves
- Hard for a security team to sign off on when the data is sensitive
Company SSO and work-email access
- Viewers sign in through your own identity provider: Okta, Entra ID, Google Workspace, and others
- Deprovisioning follows your IdP, so access ends when the assignment is removed
- Per-viewer access events give you an audit trail, not an anonymous link
- SAML-based, the same authentication path your security team already operates
This also makes the internal conversation simpler: the review is "static content behind our own IdP," not "a third party with access to our warehouse." While SSO is being configured, the trial can admit viewers by verified work-email domain, so the team gets value before the review finishes.
100 viewers. Free.
Everyone can open it. Nobody buys a seat.
Viewers are free on every plan, with no limit. The price is for publishing, not for being looked at, which is why adding the hundredth viewer costs the same as the first.
Common questions
Three things people usually want to know
"I'm not technical, is this going to be a project?"
Drag a file in, or click publish inside Claude, and you get a link back. There's no infra to set up and nothing to configure.
"Will this leak our numbers?"
There's no public URL to leak. Only people at your company can open the link, and the file sits behind your login. We never hold standing credentials to your warehouse.
"What happens when the data changes?"
Publish again, and the link stays the same. You can schedule it from Cowork to refresh on its own.
How it stacks up
Company-only access, unlimited free viewers, and no infra to set up. Most options give you two of the three. The table shows which one each gives up.
| Artifactive | Claude Native Sharing | Public Host (Vercel/Netlify) | Cloudflare Access | Email the File | |
|---|---|---|---|---|---|
| Viewers don't pay per seat | ✓ free + unlimited | ✕ seat per viewer | ✓ but no gate | ✕ per-user pricing | ✓ |
| Company-only access | ✓ by default | ~ same Work acct only | ✕ public | ✓ | ✕ forwardable |
| No infra to set up | ✓ | ✓ | ~ config + risk | ✕ | ✓ |
| Always current | ✓ refresh = re-publish | ~ | ~ | ~ | ✕ stale on send |
Pricing
You pay to publish. Viewing is always free.
A flat monthly price you can put on a card. No annual contract, no call with sales.
Team 5
$149/mo
1 admin + up to 5 publishers
- Unlimited free viewers
- Company SSO and work-email access
- Publish by drag-and-drop or from Claude
- Refresh by publishing again
Featured
Team 15
$429/mo
1 admin + up to 15 publishers
- Everything in Team 5
- Unlimited free viewers
- Room for more publishers as the habit spreads
- Priority onboarding support
14-day free trial · card required · cancel anytime
For IT & security
Built for the security review you already run
Artifactive is a static artifact gateway for internal dashboards. Dashboard files are encrypted at rest and served only after tenant-scoped viewer authentication. We don't run customer code, execute builds, proxy database queries, or maintain standing credentials to Snowflake, BigQuery, Salesforce, or your warehouse.
Identity boundary
SAML SSO through your IdP, including Okta, Entra ID, Google Workspace, Ping, OneLogin, and JumpCloud. Viewer access can be set to SSO-only, with deprovisioning following the IdP assignment.
Data boundary
Static dashboard files are stored separately from control-plane metadata. Artifactive stores tenant, site, billing, access-policy, and audit metadata, not live warehouse data or source-system credentials.
Provider posture
Runs on AWS. The underlying infrastructure carries SOC 2 and ISO 27001 attestations. Artifactive's own attestations are on the roadmap and not yet claimed.