Softsurance/Integrations
Connected honestly.
Softsurance shows an integration as active only when it’s configured and working. Here’s what exists today, what’s in preview, and what’s next.
01 / Directory
All integrations11 entries| Integration | Category | What it does | Status |
|---|---|---|---|
| Playwright · Chromium | Test engine | The browser engine behind discovery and frontend tests. | Release 1 |
| In-app notifications | Notifications | Failures, recoveries, new issues and usage warnings. | Release 1 |
| OpenAPI | API specs | Import a 3.x spec to list and select endpoints. | Preview |
| AI provider | Investigation | Any provider behind the interchangeable interface, set by environment variable. | Preview |
| Notifications | Transactional email once a provider is configured. | Preview | |
| GitHub | Source & CI | Commit and pull request metadata, linked regressions, approved-event triggers. Narrow permissions only. | Roadmap |
| PostgreSQL | Database | Read-only schema inspection and integrity checks. | Roadmap |
| Slack | Notifications | Failure and recovery messages to a channel. | Roadmap |
| Microsoft Teams | Notifications | Failure and recovery messages to a channel. | Roadmap |
| Webhooks | Events | Signed, idempotent event delivery to your endpoint. | Roadmap |
| Deployment metadata | Context | Correlate failures with the deploy that preceded them. | Roadmap |
02 / Principles
How we build integrations3 rulesI-01
Narrow permissions
We ask for the least access that does the job — read-only where possible, never broad repository scope.
I-02
Verified webhooks
Incoming webhooks are signature-checked and processed idempotently, so duplicates are harmless.
I-03
Encrypted secrets
Integration tokens are encrypted at rest and never returned by the API.