A place for the tools your team already builds. That makes each one easy to go live, easy to share, and easy to find.
Your team builds what it needs
Ops builds a supplier scorecard
Sales builds a deal desk
Finance builds a P&L projection
Hub keeps them discoverable and running
Acme Hub
Ops
Sales
Finance
Client work
And more
…
A company ends up running the way you wish, on the software you have built. Hub is where it lives.
Hub does not change the way you work. It takes away the infrastructure work you should never have had to think about.
A need for a custom tool appears
The builder describes it to an agent
The agent builds it, as a repo
The agent deploys it with the Hub skill
A link comes back, with access already set
The link works on the login they already have. No new account, no ticket, no VPN.
Access is decided before the link exists. Owner only by default, and a guest link carries a date.
It stays up without you. Logs, health and restarts are Hub’s problem, not your laptop’s.
Common applications, and what Hub settles for each.
Internal tools
- One command to deploy, filed next to everything else the team runs.
- Talks to your other tools over an internal address, with no keys in the code.
- Logs, health and a restart when the infrastructure misbehaves.
One copy per client
- The whole fleet in one view, and an update you push across the copies.
- Each copy shares separately, with its own list of who can open it.
- Secrets are settings, edited on one copy or on all of them.
One-time applications
- Slides, a demo, a handover page. Shareable the day you build it.
- A stop date on it, so it does not outlive the reason it exists.
- Guests expire on their own, and nobody has to remember to revoke.
Apply for the closed beta. Free while it lasts.
You are on the list.