Publish and share the small web tools your AI agents build, as easily as a Google Doc. Google sign-in, permissions, storage and gVisor sandboxing built in. Self-hosted.
FAQ (answers come from our records)
How do I install it?
The repository provides this install command: npm install -g sharebox-cli. It comes from the repository itself; we cannot guarantee it runs as-is in your client.
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository zalaso/sharebox;first catalogued 2026-10-10;last seen 2026-10-10。There is no official certification or quality rating here — we record sources and dates only.
ShareBox
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
**Publish and share small web tools built by AI agents — as easily as sharing a Google Doc.**
**English** · Italiano
---
Anyone can now ask an AI agent for a small tool — a team vacation tracker, a form, a dashboard. Putting it online and sharing it *safely* is the hard part: hosting, domain, HTTPS, login, database, permissions.
ShareBox removes all of that. Your agent builds the tool and publishes it with one command; you get a link and share it with specific people, a whole company domain, or anyone with the link. Visitors sign in with Google. The tool gets their name and email for free, stores its data in its own database, and runs in its own sandbox.
> *"Build a vacation tracker for my team and publish it."*
> → the agent writes it, publishes it, and replies with https://vacation-tracker-k3x9.your-tools-domain.org → you share it with @yourcompany.com → colleagues open it, sign in with Google, and add their days off.
ShareBox is **self-hosted**: you run your own instance on a small Linux server, with your domains, your Google login and your users. It is independent from any other instance.
Features
- **One-command publishing** from a terminal (sharebox publish) or straight from an AI agent through the bundled **MCP server**. Every tool gets its own HTTPS address; republishing updates the same tool and keeps its data.
- **Private by default, shared like a document**: specific people (email), every Google Workspace account of a domain, or anyone with the link — each as *can use* or *can manage*. Revocations apply on the very next request.
- **Google sign-in handled by the platform**: tools implement no login and receive a trusted identity (name, email, role).
- **Built-in storage**: every tool has its own SQLite database. Static pages use a tiny SDK with server-side permissions (sharebox.collection("vacations").add({...})); tools with server code get direct SQL access.
- **Strong isolation**: each tool runs in its own gVisor sandbox with workerd, its own network, read-only code and CPU/memory/process limits. Only one small, separate process may talk to Docker.
- **Web dashboard** for sharing, status, logs, activity, suspension and deletion — plus ready-to-copy commands to connect your computer and your agents.
- **Daily backups**, optionally copied to Google Drive encrypted.
- **Cheap**: runs on a ~4 €/month VPS; the tools' domain can be a free DuckDNS subdomain.
How it works
Every request to a tool goes through the gateway, which checks the session and the permissions, strips anything a browser could forge and injects the visitor's identity. Tools cannot reach each other, the platform, the host or the internet. Design and rationale: docs/architettura.md and the decision records in docs/adr/ (in Italian).
Quick start
**You need:** an Ubuntu 24.04 server (2 GB RAM is enough to start) with ports 80/443 free, a domain for the platform (e.g. sharebox.example.com), a domain for the tools — a free DuckDNS subdomain or a domain on Cloudflare — and a Google OAuth client.
On the server, as root:
The installer sets up Docker and gVisor, asks for your domains and credentials (secrets are not echoed), checks DNS, ports and firewall, builds everything from source, starts it and schedules nightly backups.