Identity & sessions
Understand the account behind the work. Authentication connects a person to a session through the platform's identity contract.
Security & trust
Important work deserves careful foundations.
Your financial workspace brings together sensitive records, connected services and people with different responsibilities. Understand the controls behind that work and the evidence that supports them.
Clear responsibilities
Trust begins with knowing what does what.
Garden follows the Keystone platform model: identity and sessions belong to Auth, access and entitlements belong to IAM, and billing belongs to Garden.
Roles & access
Give people and integrations access appropriate to their work. IAM owns permissions, roles, grants and entitlements.
Financial records
Keep billing accounts, usage, invoices, wallets and plans in the financial platform, with the relevant account context.
Follow the records
Keep the detail behind a decision.
Ask for the relevant records and keep them beside the explanation. Explore a review vision that makes the account, the decision and its supporting context easier to follow.
Garden, in conversationProduct vision
You
What needs a closer look before we move forward?
A little more context.
Bring the important checks into the conversation.
Identity information Supporting documentsHuman review
Illustrative dataExplore the possibilities
Evidence, on request
Ask for the current scope.
Evaluating Garden for a regulated workflow or a security review? Contact the team for the current control documentation, available reports and the scope that applies to your deployment.
Security reviews
Discuss identity, permissions, provider connections, data handling and deployment-specific controls with the Garden team.
Attestations & certifications
Certification status and report scope must be supported by current documents. Request the available evidence directly; this page does not assert a SOC 2 or ISO certification.
Responsible disclosure
Found something that needs our attention?
Send security findings to security@gardens.ml. Include enough information to identify the affected component and reproduce the issue without exposing customer data.
Good questions.
Questions about trust.
Does using Garden make my organization compliant?
Compliance depends on your business, jurisdiction, policies and implementation. Garden provides financial and review workflows; those tools do not replace your organization's responsibilities.
Where can I request security documentation?
Email security@gardens.ml with your review requirements and deployment context. The team can identify the current evidence and scope available for your review.
How should new applications integrate with identity and billing?
New L1fe applications integrate through Keystone. Auth owns identity and sessions, IAM owns access and entitlements, and Garden owns billing.
Where can I read about data handling?
Read Garden's privacy policy and contact privacy@gardens.ml with questions about your account or deployment.