Live telemetry, demo data: 14 access sessions active, 30 queries a minute.
/access
Every request approved. Every query on the record.
Access is approved for a set window and ends on its own. Every query a person, bot, or agent runs is on the record, as it happens.
People3
Bots3
Your agents3
Data apps3
Worth a look · by source · 30 days
Queries · 30 days
48,230
Sessions active
14
Worth a look
1.6%
Writes
0
01 · Approved access
Approved for a set window. Then it ends.
Access to data is requested with a reason, approved by the people your team names, and open for a set window. When the window closes, the access ends on its own. Revoke it sooner with one click.
Pick a window and watch a request run its course. Every query inside it lands on the record.
Duplicate payment reviewpi.analyst@demo-plan.com · claims_dw, provider_master · read-only
Ended on its own · 9 queries on the record
Demo data
Answer replay · Run 0193 · Demo dataComplete · 11.5s
Turn 05 · SQLjoin claims.claim_header on claim_id
Ran aspi.analyst · session 8h · read-only
Result1,102 rows · 3.4s · Worth a look · status filter misses partial denials
02 · The audit trail
Replay any answer, turn by turn.
Each answer keeps its own record: planning time, query time, rows returned, and when a check found something.
Pick any turn to see who it ran as and what came back.
- Model time apart from your database’s
- Every query with its rows and its session
- Every check pinned to the moment it fired
03 · People
Who is asking, and how it is going.
Activity by person and team, each with the share of answers a check marked worth a look. See where questions come from, and which teams the knowledge graph serves least well.
Usage · last 30 days · Demo data47 active · 9 dormant
Seat map · 56 seats
- Ranked by queriesWorth a look
- Signal
- Medicare connection not granted
- Last run
- Monday 7:00 AM · 0 of 5 measures
- Fix
- Request read access to connection 2
04 · Resources
Find the one that needs attention.
One view for every bot, app, and dashboard: how often it runs, who uses it, and what it can reach. A bot asking for data outside its scope, or an app no one opens that still holds access, shows up here.
05 · Standards
Audited every year.
HITRUST i1
Certified. The certification letter is public in the security portal.
SOC 2 Type 2
Security, availability, confidentiality, and processing integrity. Unqualified opinion, no exceptions noted.
Annual HIPAA audit
Against the HIPAA Security and Breach Notification Rules, every year. We sign BAAs.
Annual penetration test
An independent firm tests the applications and external network against OWASP application and LLM standards.
Role-based access
Each person sees what their role allows, and privileged accounts use multi-factor authentication.
Access reviewed
Grants are reviewed periodically, and every request ends on its own when its window closes.
06 · Questions
What a review will ask.
What does the audit trail record?
Who ran what, against which data, and when, for people, bots, apps, and agents alike. Every answer also carries its own receipt. It lists the queries it ran, the rows they returned, and the checks on the result.
Who approves access?
The approvers your team names. Access is requested with a reason, approved for a set window, and ends on its own when the window closes, or sooner if someone revokes it.
Do bots and agents get the same controls?
Yes. Bots work on approved, time-limited access and are read-only by default. Your own agents read the approved knowledge, and every read lands on the record.
Can we see the reports?
Certifications are public in the security portal, and the SOC 2 Type 2 report and HITRUST validated assessment are available on request. We sign BAAs.
See every query, on your own data.
Connect one system and watch the record build: every request, every session, every query, and every check.