SECURITY AND RELIABILITY

Connect your tools with clear rules.

Vela’s principles for access management, validation and execution, explained simply.

Access per client account

Each installation uses the access belonging to that account. Reusing a connector for another client does not replace that client’s own sign-in.

Vela uses AES-256-GCM to encrypt secrets stored by the service. Supply client access through the sign-in flow provided inside the product.

Passive checks must not perform business mutations. A write with an unknown outcome is not automatically retried.

A check that did not run remains unverified. Input, authentication, software-change and execution errors are distinguished to guide resolution.

Supported changes go through repair and validation. A rejected session may require the client to sign in again; repair is not a universal guarantee.

Connect accounts and actions you are authorized to use. For sensitive data or specific requirements, clarify the scope before going live.

Describe your use case and organizational requirements. Our team can clarify the conditions relevant to your project.