# Publidock

> Publidock gives the artifacts your AI makes — dashboards, docs, prototypes — a live URL your team can open. It publishes any static file (HTML, PDF, markdown, CSV, an image, or a folder) behind company sign-in, a named list, or an expiring password.

Publidock is not git-connected hosting. There is no repository to connect and no framework to detect. The file is the input. Viewers sign in with the account they already have and do not become members by opening a link. Customer-published sites are served on a separate domain and are not indexed.

## Product
- [Publidock](https://staging.publidock.com/): Your AI made it. Now share it with your team
- [Pricing](https://staging.publidock.com/pricing): Priced by live sites, never by people. Viewers are never charged
- [Self-hosted](https://staging.publidock.com/self-hosted): One Go binary, no Kubernetes. Licensed per instance: Standard or Enterprise
- [Docs](https://staging.publidock.com/docs): How it works. HTTP API, CLI, MCP, and CI — one POST
- [Security](https://staging.publidock.com/security): What we do, and what we have not done yet

## Writing
- [Blog](https://staging.publidock.com/blog): Why the product is this shape
- [Share a vibe-coded prototype with your team](https://staging.publidock.com/blog/share-a-vibe-coded-prototype): If it runs in the browser, it can have a live link your team signs in to see. What works, what does not, and the one setting a single-page app needs.
- [Rendering is not sharing](https://staging.publidock.com/blog/rendering-is-not-sharing): Slack now shows an HTML attachment inside the channel. That fixes looking at one file. It does not give the file an address, a door, or a current version.
- [There is no repo to connect](https://staging.publidock.com/blog/there-is-no-repo-to-connect): Git-connected hosting assumes a repository and a build. The people who produce these files have an export.
- [One rule, set by the person who published it](https://staging.publidock.com/blog/one-rule-per-site): A bucket policy is a ticket. A project-wide lock is an admin setting. A dashboard needs a door of its own.
- [Mark the chart they mean](https://staging.publidock.com/blog/mark-the-chart): Feedback in a separate thread is how the dashboard dies in a DM. Comments belong on the artifact.
- [Priced by sites, never by people](https://staging.publidock.com/blog/priced-by-sites-never-by-people): Seat math punishes the moment someone publishes. Viewers and members are unlimited. You pay for live URLs.
- [No Kubernetes. No exceptions.](https://staging.publidock.com/blog/no-kubernetes-no-exceptions): The identical product is one Go binary against your Postgres and your bucket. The files never leave your network.
- [The assistant that built it can ship it](https://staging.publidock.com/blog/the-assistant-ships-it): If an agent just wrote the artifact, handing you a zip is the old Slack problem. The tool result should be a live URL.

## Optional
- [llms-full.txt](https://staging.publidock.com/llms-full.txt): The same facts as a single page of Q&A
- [Changelog](https://staging.publidock.com/changelog): What changed, and when
- [Status](https://staging.publidock.com/status): Live component health for this instance