Your AI generated the report. Your company should own it.
Publish, govern and preserve AI-generated business knowledge independently from any AI vendor.
Works with Claude, ChatGPT, Gemini, Codex, and MCP-compatible agents.
From AI conversation to shared report.
The useful work already happens in your AI tool. publishwith.ai handles the step after: turning that output into a live link people can actually use.
Ask your AI
"Build the revenue dashboard and publish it for the exec team." No export, upload, deploy, or manual formatting step.
Get a live link
The report stays native: HTML, Markdown, charts, tables, and data-backed pages render in the browser instead of being flattened into a file.
Keep control
Update the same link, restrict who can open it, revoke public access, and keep a record of versions and views.
Built for people who turn AI output into business work
The report is useful. The sharing is still broken.
AI can already produce the dashboard, briefing, or analysis. The mess starts when you need another person to open the result.
Charts stop being interactive, data goes stale, and the next update means rebuilding the package again.
Stakeholders ask for the latest version, old files keep circulating, and nobody knows which copy is current.
Once a report leaves the chat, you still need updateability, revocation, access control, and a record of what was shared.
Use it where an AI report should become the source of truth.
Executive reporting
A board-ready link that stays current instead of a slide deck everyone forwards.
Live reports Team+
On Team and Enterprise, your AI can publish sandboxed Python that queries data and pulls approved external APIs, then re-renders on demand or on a schedule. The credential stays with your admin; the report just refreshes.
Client & partner delivery
Keep a reusable group for each external client or partner, then direct every report you generate to them under access control, and revoke when the engagement ends.
Control is built into the link.
The first value is a report people can open and use. The second is that the same report can be restricted, revoked, versioned, and audited.
Corporate SSO
OIDC support for Azure AD, GitHub, Keycloak, and other identity providers.
Per-artifact ACLs
Owner, editor, and viewer roles for users and groups.
HTML sanitization
Uploaded HTML is sanitized and served with restrictive CSP headers.
Audit logging
Publish, view, access, and admin actions are logged with actor identity.
Guarded SQL
Agents can work with data while destructive operations stay classified and controlled.
Share links
Public read-only links are revocable, token based, rate limited, and tracked.
Encryption at rest
Every published file is encrypted with AES-256-GCM and a per-artifact key. Your content is protected even if storage is compromised.
GDPR-ready, hosted in Germany
All workspaces, databases, share links, and audit logs reside in the EU. No data leaves European infrastructure.
Audit evidence for AI governance
Exportable audit trail covering who published what, when, with which version, and who accessed it. The evidence GDPR and emerging AI Act oversight expect, ready to use inside your own framework.
For IT, this is governed publishing instead of another unmanaged link.
Business teams get a faster way to share AI output. IT gets a controlled distribution layer, not a new pile of shadow deploys.
Business users keep moving
They ask the AI for a report and receive a link. They do not need to learn hosting, deployment, or artifact management.
IT keeps visibility
Admins and owners can see what was published, what version is live, who has access, and which links can be revoked.
BI remains the system of record
Use publishwith.ai for AI-generated briefings, client packets, temporary dashboards, and narrative analysis around your existing tools.
Evaluating this for your organization? The governance page covers SSO, audit, access control, EU hosting, and security posture.
Governance for IT & security teamsWhat changes compared with the usual workarounds.
The difference is not another place to store files. It is a direct path from AI output to a live report link.
| Outcome | Email / Slack | Shared drive | Static hosting | publishwith.ai |
|---|---|---|---|---|
| AI publishes directly | - | - | - | Yes |
| Report stays interactive | - | Partial | Yes | Yes |
| Same link can be updated | - | Manual | Manual | Yes |
| Revocable external sharing | - | Limited | - | Yes |
| Per-report access control | - | Limited | - | Yes |
| Data-backed dashboards | - | - | - | Yes |
| Version and access history | - | Limited | - | Yes |
| No rebuild into slides or PDFs | - | - | - | Yes |
Simple, transparent pricing
All features are unlocked during early access. Billing starts when we launch — early-access users get advance notice and a grace period.
Free
Personal projects and experimentation
- ✓ 1 user (single account)
- ✓ 5 artifacts in your workspace
- ✓ 5 MB total database (shared across artifacts)
- ✓ 3 share links per user
- ✓ Built-in auth & social login
- ✓ HTML, Markdown, dashboards, and data-backed artifacts
- ✓ MCP access
- ✓ Default CDN allowlist: jsDelivr only
- ✗ Live Python reports (sandboxed)
- ✗ Full-text content search
- ✗ Custom OIDC / SSO
- ✗ Managed CDN allowlist
- ✗ Account deleted after 30 days inactivity
Team
Teams and production workloads
- ✓ Up to 20 users in your workspace
- ✓ 50 artifacts in your workspace
- ✓ 50 MB total database (shared across artifacts)
- ✓ 20 share links per user
- ✓ Built-in auth, social login & 1 OIDC provider
- ✓ HTML, Markdown, dashboards, and data-backed artifacts
- ✓ MCP access
- ✓ Live Python reports — sandboxed, with governed API connections
- ✓ Full-text search across all artifact content
- ✓ Admin-managed CDN allowlist
- ✓ Active as long as subscription is paid
- ✗ Multiple OIDC providers
- ✗ Advanced CDN dependency policy
- ● Custom subdomain (yourteam.publishwith.ai) Phase 2
Enterprise
Enterprises with security and procurement needs
- ✓ Up to 200 users in your workspace
- ✓ 500 artifacts in your workspace
- ✓ 1 GB total database (shared across artifacts)
- ✓ 200 share links per user
- ✓ Multiple OIDC / OAuth2 providers
- ✓ HTML, Markdown, dashboards, and data-backed artifacts
- ✓ MCP access
- ✓ Live Python reports — sandboxed, with governed API connections
- ✓ Full-text search across all artifact content
- ✓ Active as long as subscription is paid
- ✓ Advanced CDN dependency policy
- ✓ Security review, SLA, and priority support
- ✓ Need more? Limits extendable on request
- ● Custom subdomain (yourteam.publishwith.ai) Phase 2
On-premise & air-gapped
Self-hosted for enterprise
Run publishwith.ai entirely inside your own infrastructure. Full data sovereignty, your security perimeter, dedicated support and custom SLA. Tailored to your compliance and procurement needs.
GDPR-ready. Hosted in Germany. All workspaces, databases, and audit logs reside in the EU.
Prices are indicative and may change before general availability. Early-access users will receive advance notice before billing begins.
Frequently asked questions
Is it free? What's the catch?
What do I actually publish?
Do I need to know HTML or deploy anything?
Why not just export the report to PDF or slides?
Where is my data hosted?
What is MCP and why does it matter?
Can I use my own identity provider (SSO)?
Is each artifact’s database isolated from other artifacts?
Can my AI build live reports that pull from our own data and APIs?
Can I upload multiple files per artifact?
What happens to my artifacts when billing starts?
What does “inactivity deletion” mean for Free accounts?
What happens to my Team or Enterprise account if I stop paying?
Why is jsDelivr the only external CDN allowed by default?
cdn.jsdelivr.net, so AI-generated reports can use common libraries like Chart.js without opening every artifact to arbitrary third-party scripts. This keeps the security model simple to audit. Team workspaces can use an admin-managed CDN allowlist; Enterprise workspaces can define stricter CDN dependency policies through security review. You can also publish libraries as local artifact files.Publish your next AI report as a live managed link.
Keep the output native, share one current version, and retain control when the report leaves the chat.