Identity and Access
Microsoft Entra ID sign-in with role-scoped access across organizations and projects.
Accountable by design
Run real work with agents, accountable by design.
Governance tools watch AI they do not run. Agent platforms run AI they do not truly govern. Renly does both: the agents do the work, and every action leaves an evidence trail. Specialist agent templates connected to Azure DevOps, Jira, Slack, GitHub, OneNote, and Dynamics 365, with tasks, notes, persistent context, an enterprise wiki, and knowledge management built in. Every agent action is attributable, passes through approval gates before it writes, and lands in a correlated audit trail. Accountability built into the runtime path, not bolted on after.
Product Experience
Natural conversation, real project data, governed actions
Chat
Wiki
Processes
Relations
Reports
Developer Agent
Analyzing dependency tree for the payment-service module. Found 3 packages with known vulnerabilities:
express-session 1.17.1, CVE-2024-xxxx (High)
jsonwebtoken 8.5.1, CVE-2024-xxxx (Medium)
lodash 4.17.20, CVE-2024-xxxx (Medium)
I can create work items for each vulnerability in your Azure DevOps backlog with severity labels and remediation notes. Approve?
Tool: analyze_dependencies → GitHub + Azure DevOps
Architecture
Your controls stay tight as you scale
Identity, approvals, and audit trails sit in the core. Integrations plug in at the edges. Add more connectors without loosening your safety rules.
Approval Workflow
Write actions are previewed and require explicit user approval before execution.
Model Gateway
Provider routing and invocation use configured providers and plan-allowed model tiers.
Effects + Audit
External writes follow controlled execution paths and security-relevant actions are logged.
Execution Controls
Open edges, closed governance core
Core runtime controls are live in Renly today, with optional extended governance deployments for stricter compliance requirements.
Ingress
Validates request shape, tenant scope, and correlation IDs.
Enforced
Identity
Organization and role-scoped permissions are checked before actions.
Enforced
Model Routing
Routes to configured providers and model tiers allowed by plan.
Enforced
Write Proposals
Create and update actions are previewed before execution.
Enforced
Effects
Writes execute only after user approval when action type requires it.
Enforced
Audit Logs
Execution and admin actions are logged for operational and compliance review.
Enforced
System Coverage
Works across all your systems. Add industry packs as you grow.
Renly connects to any system out of the box. Turn on domain-specific packs for healthcare, finance, legal, or manufacturing when your team needs them.
Core Platform Packs
System-neutral capabilities used across departments.
- Policy templates and approval routes
- Execution observability dashboards
- Cross-system task orchestration
Enterprise Ops Packs
Horizontal workflows for regulated and process-heavy teams.
- Support operations triage and response
- Revenue operations account workflows
- Compliance and audit evidence workflows
Delivery Intelligence Pack
Project and ADO depth remains valuable but becomes one pack.
- Backlog and sprint execution insights
- Engineering and QA workflow support
- Delivery reporting with governed writes
By the Numbers
What you get on day one
2
paid tiers with audit-log access (Pro Plus and Enterprise)
4
plan tiers: Free, Pro $19.99, Pro Plus $49.99, Enterprise
Broad
tool and connector action coverage
5+
model-provider options including BYOLLM
0
uncontrolled AI writes, every action is approval-gated
AI agents that connect to your systems and follow your rules
Renly runs governed AI agents across your business systems, from engineering sprints to legal compliance to customer operations, in one platform.