Skip to content

Free · Apache-2.0 · API tokens are free

SDODS — an automation platform with a reusable architecture

BDD for UI, API and hybrid flows. Multi-project, multi-environment, data-driven and self-healing, with before/after screenshot narratives, a database-backed history, an MCP server, AI agents, GitHub and Jira integration and a web UI.

Install SDODSRead the docs

Install in one line, on any operating system:

curl -fsSL https://sdods.com/install.sh | sh

Why SDODS

Software ships when someone is confident enough to say yes. That confidence is usually scattered across a green pipeline, a manual check and a screenshot in a ticket. SDODS turns it into evidence anyone can point at: every scenario tied to a business capability, every run reproducible from one command, every regression explained by the screenshots and requests that produced it.

UI, API and mixed scenarios in one language

Gherkin with one merged fixture set, so a scenario can seed through the API and assert in the browser.

Many apps, many environments

One YAML per project plus one per environment; strict, explainable configuration precedence; secrets only through ${VAR}.

Reusable data

CSV, JSON, YAML, database tables and faker factories per environment, plus user pools leased per worker with login-state reuse.

Confidence across browsers

Chromium, Edge, Firefox, WebKit and mobile emulation; --project-matrix runs every browser you declared, @skip:<browser> is validated by lint.

Readable results

Before/after screenshots per step by suite tag, API request/response snapshots, and a run viewer with slider, overlay and pixel diff.

Institutional memory

Cucumber NDJSON ingested into SQLite or Postgres: flakiness, locator fragility, environment stability and suite health over time.

How it works

Everything is CLI-first. The web UI, the MCP server and the scheduler spawn the same commands and stream their output, so CI needs nothing but Node and the repository.

  1. sdods CLI
  2. Config + registry
  3. Browser runs
  4. NDJSON + screenshots
  5. SQLite / Postgres
  6. Web UI · MCP · agents

See every step

Regression scenarios capture a screenshot before and after every UI step. The run viewer pairs them with a slider, an overlay and a pixel diff. These are real captures from the demo project.

SauceDemo login form filled in, before the login button is clicked
Before: login form, credentials filled
SauceDemo inventory page after the login step
After: inventory page, logged in
SDODS run viewer showing the step timeline with a before/after comparison
Run viewer: step timeline with before/after comparison and API panels

What ships in the box

BDD for UI, API and hybrid

Reusable step library, page objects with decorators, module and process taxonomy.

Data and user pools

Per-environment datasets, factories, leased accounts, cached storage state.

Self-healing locators

Scored candidate probes, persisted heal history, proposals to fix page objects.

Before/after narratives

Screenshot policy by suite tag; visual baselines; API snapshots.

SQLite or Postgres

One schema, runtime toggle, verified switch in both directions.

MCP server and agents

84 tools for Claude Code, Codex, Cursor, VS Code, Gemini CLI and any MCP client; a Claude Code plugin; planner, generator, healer, upgrader.

GitHub and Jira

Check runs, PR comments, deduplicated issues, @jira:KEY links, transitions.

Schedules

Cron recipes with overlap policy; runs from the server, crontab, launchd, systemd or Actions.

Web UI with roles

Organizations, workspaces, projects, modules; run viewer, Gherkin editor, tokens.

Quickstart

curl -fsSL https://sdods.com/install.sh | sh   # or on Windows: irm .../install.ps1 | iex

cd ~/.sdods/app
sdods run -p demo-shop -e staging -l api
sdods run -p demo-shop -e staging -l ui -b chromium -t @smoke

Only Node 22 is required. Options, upgrade and uninstall are on the install page and in the installation guide.

Works with your AI coding tools

Claude Code, Codex, Cursor, VS Code, Gemini CLI, Windsurf and any MCP client. Install the plugin or the skills, then ask your assistant to plan, write, run, heal or review tests. Agents reuse your logged-in CLI session, so no API key is required.

A team can also share one SDODS server and connect every assistant to its /mcp endpoint with a scoped token. The AI coding tools guide covers each client.

Using an AI coding agent? Install SDODS:

Install the SDODS plugin in Claude Code: skills, subagents, commands and the MCP server.

  1. /plugin marketplace add siri1410/sdods-skills
  2. /plugin install sdods@sdods
Every tool, the MCP endpoint and skills

Want a feature? Tell us.

Feature requests and feedback go straight to the maintainers by email. No account with us, no tracking.

Send feedback