Jira Intake
Select a Jira ticket, inspect architecture impact, and start a tracked Ripple ChangeSet.
Subscription
Activate local access before running Jira, indexing, agent, verification, and delivery tasks. Login is stored by the local Ripple backend.
Account
Local Setup
Configure provider credentials for the features you want to use. Missing credentials only fail the feature that needs them.
Service Map
Microservice connections, exposed APIs, downstream callers, events, and shared resources.
Select a service
Click a microservice to expand its endpoints and connection evidence.
Service Graph
Open the interactive graph to inspect service connections and drill into APIs.Tickets
No tickets loaded
Select a ticket
Ticket detail appears here.
No ticket selected
Load Jira tickets and choose one to begin.
Approval is required before creating a ChangeSet.
Start implementation to see the agent plan, active step, repository work, and result.
Delivery Overview
Current ticket health, impact shape, and delivery progress.
Impact Mix
0 nodesWorkflow
Not startedWhat Ripple Understood
Ticket interpretation, assumptions, and candidate solution paths.
Impact Analysis
Primary ownership, blast radius, confidence, and risk.
Change Plan
Ordered service work and required evidence gates.
ChangeSet
Coordinated delivery state for the selected ticket.
Operations
ChangeSets, repository coverage, impact graph, MR state, and verification evidence.