Pubto is a local-service publishing platform for AI development and remote collaboration. It publishes selected demos, web products, APIs, WebSockets, TCP services, files, folders, and static websites to controlled public endpoints, and can map a shared endpoint back to localhost.
FAQ
Questions about publishing local services and files?
Answers about the Desktop app, AI integrations, local mappings, file publishing, security controls, plans, and release boundaries.
Start with the target and the intended recipient.
Choose one demo, web product, API, service, file, folder, or website. Pubto gives that publication an independent address, state, expiry, usage controls, and revoke action.
Read the getting started guideNo. Install Desktop on the computer that can reach the target, choose one service or file, and create an endpoint through the Pubto Relay Network.
No. Pubto requires an account before publishing or using account features.
Desktop has managed integrations for Codex CLI, Claude Code, OpenCode, Gemini CLI, pi, and Grok CLI. Installation is offered only when that tool's configuration directory exists.
You can install Pubto Skill first; the first publish action guides you to Desktop when the local publisher is needed. Or install Desktop first, open AI & Skills, and add the Skill to the AI tools you use.
Yes. Publish the selected file from the computer that stores it. Visitors can preview supported PowerPoint, PDF, Word, Excel, image, text, Markdown, and CSV formats or download the original through the same protected endpoint.
Yes, on a plan that supports TCP and the intended target scope. Publish an authorized short-lived MySQL endpoint from the office side, keep database authentication and TLS enabled, and map it to a loopback port on the home computer.
Yes. Publish only the API, WebSocket, HTTP, or TCP target the team needs, choose a short expiry and appropriate access policy, and revoke it after the integration session.
Yes. Create independent endpoints, then place them in one public collection. Each item keeps its own target, public address, access policy, expiry, and availability state.
Pubto is currently an early-access deployment and does not publish a geographic coverage or SLA commitment. Desktop uses the Relay assigned by Control; self-hosted Relay enrollment remains a deployment preview.
A permissioned remote terminal experience is planned. It is not part of the current public release.
No. Pubto is designed for development previews, temporary sharing, remote collaboration, and controlled service access. Use production hosting, backups, and your own availability controls for permanent public services.
Pubto is pre-launch and public checkout is not live. No paid plan can be purchased today. Before billing opens, pricing and checkout will show the exact currency, billing interval, renewal, included usage, taxes, cancellation, and refund terms.
No. Current automated controls inspect selected publication metadata and normalized public source hostnames and enforce usage limits. Pubto does not log request or response bodies by default or claim to inspect every file byte or encrypted stream. A reported public endpoint may receive limited human review when necessary for safety, legal, or abuse response.
Still need help?