Dokven is an AI-supercharged QA platform. You draw a user journey (signup, login, checkout) on a visual canvas, then run it in a real browser with video and self-healing AI selectors. Behind every step it also runs a full toolbox of audits: SEO, security headers, performance, accessibility, copy, API, responsive, and analytics tags, plus AI-generated test plans.

Is there a free website QA and testing tool?

Yes. Dokven has a free tier with all 10 tools and free tokens that never expire, with no credit card and no SDK required. You can also try any tool on any URL as a guest before you sign up.

How do I test a checkout or login flow without writing code?

In Journey Studio you drag the steps of the flow onto a canvas (open a page, fill a form, click, assert). A real Chromium browser runs it end to end and records video, so there are no selectors to hand-write. Self-healing AI locators keep the run going when the page changes.

Does Dokven check SEO, performance, accessibility, and security too?

Yes. Point one tool at any URL or run them all together. You get real-browser Core Web Vitals, WCAG 2.2 accessibility, TLS/CSP/header security, an SEO crawl with schema validation, copy and analytics-tag audits, and responsive snapshots, with an AI crosswalk that connects findings into one root cause.

Do I need to install anything?

No. Dokven runs entirely in the browser against any public, staging, or pre-launch URL. There is no SDK, agent, or browser extension to install. A REST API and CLI are included for wiring runs into CI.

Can Dokven monitor a site on a schedule?

Yes. Save a journey and put it on a daily or weekly schedule. Dokven re-runs it in a real browser and alerts Slack, Discord, or a webhook the moment a score regresses or a flow breaks.

Dokven

– Tokens Left Sign In Get Started

– Tokens Left

Developer Workflow

Integrations

Every recipe on this page runs against the live API today. Copy, paste, done. Create a key on the API keys page; scans authenticated with it use your token balance and save to your run history.

REST API

One POST per tool. Responses include the score, grade, every check, and the AI summary, the same data the web reports render. The full schema lives in the OpenAPI spec.

bash

# Full Stack Scan: SEO, security, performance, accessibility, copy, responsive, tags
# in one call. Authenticate with your dk_… key (the full scan costs more
# tokens than the guest tier holds; single-module endpoints work as guest).
curl -X POST "https://www.dokven.com/api/scan/all" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer dk_YOUR_API_KEY" \
  -d '{"url": "https://example.com"}'

Endpoints

Full Stack ScanPOST /api/scan/all
API HealthPOST /api/test-api
SEO AuditPOST /api/seo-audit
Security HeadersPOST /api/security
PerformancePOST /api/performance
AccessibilityPOST /api/accessibility
Copy TestingPOST /api/copy-testing
ResponsivePOST /api/responsive-testing
Tag AuditPOST /api/tag-audit/scan

CI quality gates

Run a Full Stack Scan against your staging URL on every pull request and fail the build when the score drops below your gate. No SDK, no package install. Each recipe is self-contained.

.github/workflows/dokven.yml

name: Dokven QA gate
on: [pull_request]

jobs:
  dokven:
    runs-on: ubuntu-latest
    steps:
      - name: Dokven Full Stack Scan
        env:
          DOKVEN_API_KEY: ${{ secrets.DOKVEN_API_KEY }}
        run: |
          curl -fsS -X POST "https://www.dokven.com/api/scan/all" \
            -H "Content-Type: application/json" \
            -H "Authorization: Bearer $DOKVEN_API_KEY" \
            -d '{"url": "https://staging.example.com"}' -o result.json
          SCORE=$(jq -r '.score // empty' result.json)
          GRADE=$(jq -r '.grade // empty' result.json)
          echo "Dokven score: ${SCORE:-?}/100 (${GRADE:-?})"
          jq -r '.summary // empty' result.json
          if [ -n "$SCORE" ] && [ "$SCORE" -lt 80 ]; then
            echo "::error::Dokven score $SCORE is below the 80 gate"
            exit 1
          fi

CLI

A single-file script for terminal audits and CI jobs: pretty, --json, and --summary output, module selection, and a --fail-below exit-code gate.

bash

# Download once (a single dependency-free script), then run audits
# from any terminal or CI job with node 20+.
curl -fsSL https://www.dokven.com/cli/dokven.mjs -o dokven.mjs

# Full Stack Scan with pretty output
node dokven.mjs scan https://example.com

# Single module, machine-readable, CI score gate
DOKVEN_API_KEY=dk_YOUR_API_KEY \
node dokven.mjs scan https://example.com --module=security --json
node dokven.mjs scan https://example.com --fail-below=80

Slack, Discord & webhook alerts

Add a webhook under Monitoring and Dokven posts when a watched URL's score regresses past your threshold, formatted natively for Slack and Discord, or raw JSON for anything else. Verify deliveries with the signature header:

verify-signature.mjs

// Every delivery is signed: hex HMAC-SHA256 of the raw request body
// using your webhook secret, sent in the X-Dokven-Signature header.
import { createHmac } from "crypto";

export function verifyDokvenSignature(rawBody, signature, secret) {
  const expected = createHmac("sha256", secret).update(rawBody).digest("hex");
  return expected === signature;
}

Ready to wire it up?

Create an API key, drop a recipe into your pipeline, and your next deploy ships with a QA gate.

Create an API key

Dokven

– Tokens Left Sign In Get Started

– Tokens Left

Developer Workflow

Integrations

Every recipe on this page runs against the live API today. Copy, paste, done. Create a key on the API keys page; scans authenticated with it use your token balance and save to your run history.

REST API

One POST per tool. Responses include the score, grade, every check, and the AI summary, the same data the web reports render. The full schema lives in the OpenAPI spec.

bash

# Full Stack Scan: SEO, security, performance, accessibility, copy, responsive, tags
# in one call. Authenticate with your dk_… key (the full scan costs more
# tokens than the guest tier holds; single-module endpoints work as guest).
curl -X POST "https://www.dokven.com/api/scan/all" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer dk_YOUR_API_KEY" \
  -d '{"url": "https://example.com"}'

Endpoints

Full Stack ScanPOST /api/scan/all
API HealthPOST /api/test-api
SEO AuditPOST /api/seo-audit
Security HeadersPOST /api/security
PerformancePOST /api/performance
AccessibilityPOST /api/accessibility
Copy TestingPOST /api/copy-testing
ResponsivePOST /api/responsive-testing
Tag AuditPOST /api/tag-audit/scan

CI quality gates

Run a Full Stack Scan against your staging URL on every pull request and fail the build when the score drops below your gate. No SDK, no package install. Each recipe is self-contained.

.github/workflows/dokven.yml

name: Dokven QA gate
on: [pull_request]

jobs:
  dokven:
    runs-on: ubuntu-latest
    steps:
      - name: Dokven Full Stack Scan
        env:
          DOKVEN_API_KEY: ${{ secrets.DOKVEN_API_KEY }}
        run: |
          curl -fsS -X POST "https://www.dokven.com/api/scan/all" \
            -H "Content-Type: application/json" \
            -H "Authorization: Bearer $DOKVEN_API_KEY" \
            -d '{"url": "https://staging.example.com"}' -o result.json
          SCORE=$(jq -r '.score // empty' result.json)
          GRADE=$(jq -r '.grade // empty' result.json)
          echo "Dokven score: ${SCORE:-?}/100 (${GRADE:-?})"
          jq -r '.summary // empty' result.json
          if [ -n "$SCORE" ] && [ "$SCORE" -lt 80 ]; then
            echo "::error::Dokven score $SCORE is below the 80 gate"
            exit 1
          fi

CLI

A single-file script for terminal audits and CI jobs: pretty, --json, and --summary output, module selection, and a --fail-below exit-code gate.

bash

# Download once (a single dependency-free script), then run audits
# from any terminal or CI job with node 20+.
curl -fsSL https://www.dokven.com/cli/dokven.mjs -o dokven.mjs

# Full Stack Scan with pretty output
node dokven.mjs scan https://example.com

# Single module, machine-readable, CI score gate
DOKVEN_API_KEY=dk_YOUR_API_KEY \
node dokven.mjs scan https://example.com --module=security --json
node dokven.mjs scan https://example.com --fail-below=80

Slack, Discord & webhook alerts

verify-signature.mjs

// Every delivery is signed: hex HMAC-SHA256 of the raw request body
// using your webhook secret, sent in the X-Dokven-Signature header.
import { createHmac } from "crypto";

export function verifyDokvenSignature(rawBody, signature, secret) {
  const expected = createHmac("sha256", secret).update(rawBody).digest("hex");
  return expected === signature;
}

Ready to wire it up?

Create an API key, drop a recipe into your pipeline, and your next deploy ships with a QA gate.

Create an API key