Delivery, end to end, in one place
Circuvent DevOps brings every pull request, pipeline and security alert across our repositories together, and joins them to the work they belong to in CV-365 — so what engineering is building and what the business planned stop being two different stories.
Secured by auth.circuvent.com — the same account you already use.
7
4
2
Fix duplicate notification on task reassignment
Circuvent-Technologies/cv-365
Rotate signing keys without invalidating sessions
Circuvent-Technologies/auth-circuvent
Leave balance accrual for mid-cycle joiners
Circuvent-Technologies/hrms-circuvent
One
queue for every repository
Two-way
links with CV-365 tasks
SSO
across the whole suite
Zero
third-party trackers
Everything delivery touches, without the tab sprawl
Eight surfaces, one session, one organisation. Each answers a question someone on the team asks every day and currently answers by opening four other things.
Every pull request, one queue
Open work across all watched repositories in a single review queue, sorted by what is actually blocked on you — not by which repository it happens to live in.
Joined to CV-365
Link a pull request to its task and the two stay in step. The task carries its branches, commits and reviews; the pull request knows what it was for.
Pipelines that explain themselves
Workflow runs with the failing step surfaced, so a red check is a diagnosis rather than a link to seven minutes of log scrolling.
Security in the same view
Dependency, code scanning and secret alerts sit beside the code they affect, ranked by severity across the whole organisation.
Repositories you choose
Watch the repositories that matter to your team. Everything else stays out of the way, and nothing is inferred from an access token's blast radius.
Standup, already written
Yesterday, today and blockers assembled from what actually happened — merges, reviews, task transitions — and editable before you share it.
Shift and on-call, in one place
Start a shift, work the checklist, log what happened and hand over cleanly. Who is covering and what came in stays next to the work.
Insights that change decisions
Cycle time, review latency and throughput measured per repository and per team, so a slow week has somewhere to point.
Three steps, then it is just there
Setup is a few minutes once, per organisation. After that the dashboard follows the repositories you told it about and stays out of the way.
Sign in with Circuvent
One account, the same one that opens CV-365, HRMS and Mail. No new password, no separate directory to keep current, no local user table to leak.
Connect GitHub
Add a fine-grained token once. It is encrypted at rest and scoped to your organisation — the dashboard reads what you have already granted and nothing beyond it.
Watch what matters
Pick the repositories your team owns and bind them to CV-365 projects. From then on, delivery and planning describe the same thing.
Built on what we already run
No new system of record. GitHub stays the home of the code, CV-365 stays the home of the work, and this joins them — writing the link back to the task so the connection survives outside the dashboard too.
- Pull requests, reviews, checks and workflow runs from GitHub
- Tasks, projects and development links in CV-365
- Attachments in Circuvent object storage, uploaded straight from the browser
- Sessions issued by auth.circuvent.com and shared across the suite
GitHub
Source of code
repos · PRs · actions
CV-365
Source of work
tasks · projects
Circuvent SSO
Source of identity
OIDC · PKCE
Object storage
Source of files
S3-compatible
Internal by design, not by firewall
This dashboard sees our repositories and our roadmap. It is built to deserve that.
Single sign-on, centrally revoked
Authentication happens at auth.circuvent.com. Access ends where the account ends — remove someone once and every app in the suite closes behind them.
Credentials encrypted at rest
Integration tokens are sealed with AES-256-GCM before they touch the database and are never returned to the browser, not even to the account that added them.
Scoped to your organisation
Every query is bound to the organisation on your session, resolved server-side. A request cannot reach another tenant's rows by asking differently.
Infrastructure we own
Circuvent-operated Postgres and object storage. Attachments go straight to our own bucket, and no third-party analytics ships with the page you are reading.
One account, every Circuvent app
DevOps is one surface of the Circuvent Technologies platform. Sign in once and move between them without signing in again.