Appearance
Integrations
DutyGraph uses a small set of outside services. This page says what each one does, how it connects and what it receives. It also lists the connections that are planned.
WARNING
A saved key is not a tested connection. Settings shows each key as Saved but not tested, Connected or Test failed. A test only shows that the provider accepted the key.
Today
| Service | What DutyGraph uses it for | How it connects | Status |
|---|---|---|---|
| Claude (Anthropic) | DutyGraph Agent and the model steps that fill the Company Repo | The company's own approved connection | Built |
| OpenAI | Research extraction, voice interviews, discovery drafts, transcription, and DutyGraph Agent or Strategy when no Claude connection exists | The company's approved connection; some older features use the firm's workspace key. See How DutyGraph uses AI | Built |
| Resend | Email: invitations, outreach, kickoff, receipts, reports, advisor notifications and agent plan links | The firm's Resend key and sender, or DutyGraph's platform sender | Built |
| Stripe | Payments: checkout, invoices and subscriptions | Operator keys and a webhook | Built, off unless keys are set |
| Neo4j Aura | A graph view of each company | The advisor account's own Aura database | Built, optional |
| Web push | Phone notifications for the advisor | The browser's push service | Built |
| Vercel | Hosting for the web app and the API | The deployment | Built |
AI providers
DutyGraph uses the company's own approved AI connection. It picks the company's approved Claude connection first, then its approved OpenAI connection. With neither, no AI call is made.
- Keys are encrypted on the server. They are never returned to the browser.
- The sample companies never call an AI provider.
- No AI call proposes an agent, sets a marker or a policy, builds an agent plan or computes an agent's permissions. That is code.
Set a workspace key in Settings › Research & AI keys. Set or approve a company's own connection in the account's Connections tab.
Email: Resend
There are two senders:
- The firm's sender. A Resend key and from-address in Settings › Research & AI keys. Outreach also needs the advisor's sender identity. Outreach email carries a footer and one-click unsubscribe.
- DutyGraph's platform sender. Set by the operator. It sends lead email and acknowledgments, and advisor notifications when a workspace has no Resend settings.
DutyGraph knows when Resend accepts a message. Delivery, bounce and complaint tracking is Planned.
Payments: Stripe
Stripe stays off until the operator sets its keys. Charges go to the firm's connected Stripe account by default. A deployment operator records that account today; a self-serve onboarding flow is Planned. Statements of work and offline payment methods work without Stripe.
Graph view: Neo4j Aura
PostgreSQL is the source of truth. Aura holds a replaceable copy of each company's graph.
- DutyGraph copies graph metadata only: record ids, kinds, titles, states, versions, hashes and links. It does not copy source text, audio, prompts or credentials.
- The app reads Aura only when the copy matches the current PostgreSQL record. A missing, stale or unreachable copy falls back to PostgreSQL.
- Each advisor account connects its own Aura database in Settings › Connections. Removing the connection stops later copies. It does not delete what is already in Aura.
Phone notifications: web push
Turn them on in Settings › Workspace › Phone notifications. An iPhone needs Add to Home Screen and iOS 16.4 or later. A notice says "<company>: <what happened>". It never holds answers or links. It opens the Inbox.
Hosting
The web app and API run on Vercel, with a PostgreSQL database. A maintenance job runs every 5 minutes for notifications, projections, retention and follow-ups. Operators set platform keys as server environment variables. DutyGraph never puts a key in source control or in these docs.
Other services in the code
| Service | Use | Status |
|---|---|---|
| Exa | Public web research | Built, tested with a simulated provider |
| xAI | Transcription and understanding in the Companion phone app | Built, simulated in tests |
| Cloudflare Turnstile | A challenge on the public request form | Built, off unless keys are set |
| TypeSafe Jev | Stricter checks on outreach and lead triage, per firm opt-in | Built, off by default |
Planned
| Connection | What it would do | Status |
|---|---|---|
| Okta, Entra ID, Saviynt | Read people, holdings and rulesets, read-only, set once per company | Planned. Holdings come from an uploaded access-export CSV today. |
| ServiceNow | Create the access request IAM works from | Planned. Today DutyGraph shows a "For IAM to do" card. |
| OAuth sign-in on the MCP server | Let web and mobile AI connectors add DutyGraph | Planned |
| Single sign-on (SSO) | Reviewers and employees sign in with the company's identity provider | Planned |
| OpenTelemetry run tracking | Record what an agent actually did next to what it was approved to do. Observed data is evidence. It never grants or blocks. | Planned |
In the governance sample, Okta, Entra ID, Saviynt, ServiceNow and Oracle are Simulated, and the screens say so.
DutyGraph does not collect employees' own logins to business systems. Planned identity connections are read-only service connections with the narrowest scopes each system offers.
INFO
Status. Built: Claude and OpenAI through the company's approved connection, Resend email, Stripe payments, the Neo4j Aura graph copy, web push and Vercel hosting. Simulated: Okta, Entra ID, Saviynt, ServiceNow and Oracle in the governance sample. Planned: live identity and IT service management connections, OAuth, SSO, email delivery tracking and OpenTelemetry run tracking.
Source: gitbook/product/connect/integrations.md in the DutyGraph repository.