DevQuaySign inStart a private trial
Engineering standards for people and agents

Know what applies, and why.

DevQuay holds your Design, Software, Infrastructure and Operations standards in one governed place, then tells each engineer and each coding agent exactly which rules apply to the service in front of them, where every value came from, and which exceptions are in force.

Start a private trialRead the setup docs
Private by default. Try it on sample data before connecting a repository.
Sample: fictional company
Minimum line coverageException activequality.line_coverage.minimum
60%inherited 70%
  1. Organization · NorthstarQuality standard rev 4
    70%
  2. Exception EXC-120 · approvedUntil 27 Nov 2026 · reviewed by a policy owner
    60%
  3. Effective for legacy-catalogInherited value returns on expiry
    60%
Merge maxRelease 1.2.0Evidence Unknown
How it works

Write it once. Review it. Resolve it everywhere.

  1. 01 · Author

    Standards with real values

    Write guidance in a block editor or keep it in Git. Attach measurable rules like “minimum line coverage 70%” with an owner and rationale.

  2. 02 · Publish

    Reviewed, immutable releases

    Changes go through review with an impact preview. Publishing creates a release you can pin, compare and roll back.

  3. 03 · Resolve

    The right rules for one service

    A Tier 1 service gets 90%, an ordinary one 70%, a legacy one its approved 60% until it expires. Same answer in the UI, CLI and MCP.

For coding agents

Your agent asks. DevQuay answers with sources.

Connect Claude Code, Codex or Cursor over remote MCP, or use the devquay CLI in CI. Agents get every required constraint, its source revision and a digest they can reproduce, plus approved templates and runbooks for that service.

  • Read-only by default; agents can propose drafts, never publish
  • Conflicts and missing facts come back as explicit errors, not guesses
  • Pinned bundles for offline work, clearly marked when stale
# fictional example
$ devquay context resolve --service checkout-api --env production
resolved  release 1.2.0  digest rd_7f3a9c2e1b
  Minimum line coverage   90%   org 70 → Tier 1 profile 90
  Java version            21    profile quarkus-http
$ devquay context resolve --service legacy-catalog --env production
exception Minimum line coverage 60% until 2026-11-27 (EXC-120)
What DevQuay does not do

Standards and context, not a control plane.

  • It does not deploy, run commands or touch production. Runbooks become reviewed checklists.
  • It does not mark something compliant without evidence. Unknown stays unknown.
  • It does not let an AI decide which rules apply. Resolution is deterministic.
  • It does not publish anything publicly unless you preview and choose it.

See your own standards resolve for a real service.

Start with sample data or import a few Markdown files and service manifests. Nothing is published until you review it.

Start a private trial