Security

Clear boundaries. Honest limits.

An overview of the controls implemented today, not a certification or a guarantee for every deployment.

Implemented access controls

Password-based authentication for signed-in access.
Membership-scoped spaces: a person must belong to a space to access its work.
Participant-scoped conversation visibility within an authorized space.
Operator-restricted administration.

Configurable model boundaries

Agents opt in to a fixed set of built-in tools, including subject lookups, proposed data changes, pipeline card changes, handoff, and ending a conversation. This is not an arbitrary external integration platform.

Request, cost, and time budgets are checked before model calls. They do not guarantee a hard spending cap or interrupt every in-progress call.

Model processing

Momntum uses OpenRouter for model requests. Conversation content and relevant prompt, tool, and workflow context can be sent for processing. The selected model provider also matters; review the applicable provider terms before sending sensitive information.

Deployment requirements

The application code does not enable production SSL enforcement. A production deployment must configure and verify HTTPS, secrets management, database access, backups, and operational monitoring. These requirements should not be mistaken for controls already verified by this page.

MFA, SSO, security certifications, and automated conversation-retention policies are not implemented. This early-access overview does not claim them.

Before relying on Momntum

Confirm the deployment’s controls and your data requirements. A formal security contact and incident-response commitments still need to be published.

Request access