THE PRODUCT, WITH REALISTIC WORK INSIDE
Explore Kimra building Kimra.
Follow customer feedback into engineering, walk through an incident, and inspect a reviewed release. These are fictional examples inspired by Kimra’s development—not actual customer records or outage reports.
Use this guide to jump between pages. Forms can be inspected, but changes, invitations, and email delivery are disabled.
Customer
Projects and customer requests.
Request boardRequests arranged by status.
Customer organizationsFictional customer accounts and their requests.
Support reportsA small illustrative dataset, not real operational metrics.
How do I create separate projects for our support and engineering teams?Customer reply threads and a separate private internal discussion.
An approved template should not be editableResolved customer request.
The verification email has not arrivedWaiting customer request.
Engineering
Platform and onboarding projects.
Kimra platformDevelopment of the Kimra experience.
Website & onboardingMake the first five minutes with Kimra clear and useful.
Epic → story → subtaskA populated engineering hierarchy with owners and different delivery states.
Story in reviewCustomer outcome, acceptance criteria, parent, and completed subtask.
All work and project queueSearch, ownership, overdue work and project progress across spaces.
Incident
One LSI project, with parent incidents and their ACI sub-projects.
Storage Availability below 90%Demo Large Scale Incident: storage availability falls below the 90% threshold. Coordinate response and track corrective ACI sub-projects.
Improve Visibility through dashboardsBuild dashboards and alerting that make storage availability and capacity visible.
Fix Capacity IssuesResolve storage capacity bottlenecks and verify availability recovery.
LSI parent → ACI sub-projectsOne Large Scale Incident with two corrective ACI sub-projects: dashboard visibility and capacity fixes.
Owned action itemOpen → In progress → Done, with an owner, due date, and completion evidence.
LSI project controlsOwner, status, target date, severity and project membership.
Change
Changes before approval, scheduled, and completed.
Kimra releasesProposed releases, independent approval, and validation.
Approved scheduled changeLocked scope, reviewer decision, schedule, and rollback plan.
Change awaiting approvalA complete proposal before the reviewer decision.
Completed changeA release with validation evidence and a closed lifecycle.
DNS changeCurrent and proposed records, TTL, review, and rollback.
Certificate rotationHostname, expiry, rotation method, and validation plan.
Templates
Project and issue definitions with versions and review states.
Approved and locked templateIndependent approval, captured version, and a locked definition.
Draft next versionVersion 2 can evolve while version 1 remains unchanged.
Template awaiting reviewA database-change issue type waiting for a distinct reviewer.
Approved project templateThe issue versions that new projects can use.
Certificate rotation templateAn approved starter with type-specific required information.
Deployment change templateAn approved starter with type-specific required information.
DNS change templateAn approved starter with type-specific required information.
Explore more
Preview the form; saving is disabled.
Create workChoose a space and inspect creation forms.
People & invitationsFictional teammates and roles; sending invitations is disabled.
Workspace settingsInspect configuration without changing it.
IntegrationsInspect connection setup; no live connections or secrets.
NotificationsSee the notification screen.
Customer-facing experience
Customer request portal ↗See the request form your customers use. Submission is disabled in this demo.