What is Hacker Sidekick Enterprise?
Hacker Sidekick Enterprise is a dedicated Hacker Sidekick server for your organization alone. It is not shared with other customers. Your members keep using the Hacker Sidekick Desktop app they already know; the difference is that Desktop talks to your instance instead of the public Hacker Sidekick service, and your administrators decide how that instance behaves.
What your instance is
Section titled “What your instance is”Each instance has its own web address (for example https://acme.hackersidekick.com, Hacker Sidekick
gives you yours) and serves two audiences:
| Part | Who uses it | What it does |
|---|---|---|
Admin portal at /admin |
Administrators (and, read-only, any member) | Configure model routing, org system prompt, Rules of Engagement, skills and MCP tool servers. Review members, usage and the configuration change log. |
| The instance itself | Hacker Sidekick Desktop, on every member’s machine | Answers the agent’s model requests, workspace indexing and web search, and hands Desktop your org’s policy, skills and tool servers. |
What changes for members
Section titled “What changes for members”Once a member points Desktop at the instance:
- Model requests go to your instance’s dedicated models, not the public Hacker Sidekick service. Each request is routed to your default-tier or sensitive-tier model (see Model routing).
- Your org’s skills, MCP tool servers and system prompt appear automatically, marked as coming from the organization, and members can’t edit or remove them.
- There’s nothing to buy. Plans, upgrade prompts and top-ups are hidden. Usage still shows, so people can see what they’ve consumed this month.
- Desktop’s status bar shows Managed by <your organization>.
Members keep the same Hacker Sidekick account. There’s no separate password for the enterprise instance.
What’s managed by Hacker Sidekick
Section titled “What’s managed by Hacker Sidekick”Some things are set up and run for you rather than from the admin portal:
- Creating the instance, its web address and its TLS certificate.
- Your instance’s dedicated model capacity and its models. You choose which model serves each role in the portal.
- Membership and roles: who belongs to your organization and who is an admin. See Members.
- Hosting, backups, upgrades and uptime monitoring.
Next steps
Section titled “Next steps”- Members: Connect Desktop to your instance.
- Administrators: Tour the admin portal, then work through the first-week checklist.
