Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.hopsule.com/llms.txt

Use this file to discover all available pages before exploring further.

When senior people leave, institutional knowledge often disappears. Hopsule provides governance infrastructure so decisions and memories stay structured and portable: many teams can reuse the same Capsules and Brain without losing the why.

​
Org-Wide Governance

Distribute architectural standards across dozens of teams without friction.
1

Define Policies

Your Architecture Board creates a “Security Standards” Capsule containing ACCEPTED decisions (e.g., “All endpoints must use OAuth 2.0”).
2

Distribute Capsules

Share this Capsule across all 50+ enterprise projects.
3

Advisory signals in the IDE

Developers load the Capsule into their IDEs. If someone uses a pattern that conflicts with an accepted decision (for example Basic Auth when OAuth is required), the IDE can surface a warning so humans can fix it. Hopsule informs; your merge policy stays yours.

​
Compliance & Audit Trails

Hopsule provides a reliable, immutable audit trail required for SOC2 and ISO compliance.
Once a decision is ACCEPTED, it cannot be edited; it can only be deprecated or superseded. Every action is logged in an append-only ActivityLog.
When an auditor asks, “Show me all authentication decisions from Q4,” easily filter by tags and dates to generate a comprehensive PDF. Reports include who accepted the decision, when, and the exact rationale.

​
Preserving Institutional Memory

When a senior architect leaves your organization, you don’t have to lose 10 years of database decisions.
  1. Export: Export their architectural context as a Capsule.
  2. Import: The incoming architect imports the Capsule.
  3. Understand: The new architect uses the Hopper AI chat to ask, “Why did we choose PostgreSQL over MongoDB in 2024?” and gets a precise answer grounded in historical memories.

​
Enterprise-Grade Features

Advanced Security

Enterprise SSO via Clerk, SAML/SCIM provisioning, and advanced Role-Based Access Control (RBAC).

CI and automation

Pair Hopsule with your own CI or hooks if you want extra gates. The product itself stays advisory for merges; your org chooses whether to block on top of Hopsule signals.

Self-Hosted Deployment

Keep your proprietary decisions and context strictly within your own infrastructure.

Custom SLAs

Dedicated support, custom onboarding, and enterprise-grade service level agreements.