Runmark — Know what makes your code run

Your code runs somewhere.Make sure it runs everywhere.

Runmark makes your development environment predictable. Scan, snapshot, compare, and verify everything your code depends on.

Python 3.12.10Locked
0 Secrets Leaked100% Masked
LIVE
Contract: runmark.json
Verified 2s ago
Application Code
Git Tracked • main@a81f29c
Source
Repository HEAD clean • 0 untracked diffs • origin/main in sync
SHA a81f29c
Dependencies
Django 5.1.2 • FastAPI 0.115 • uv.lock
Locked
System & Runtime
Python 3.12.10 • Node 22.19.0
Verified
Environment & Services
Postgres 16.3 (Port 5432) • .env secrets
Healthy
R
Environment Match
ce19840a...
100% In Sync

Trusted with the tools you already use

Python
3.10, 3.11, 3.12, 3.13
Django
4.x, 5.x Frameworks
FastAPI
ASGI • Modern APIs
Next.js
React & Node Runtimes
Node.js
v20, v22 LTS
Docker
Compose & Containers
PostgreSQL
v14, v15, v16
Git
Repositories & Branches
uv & pip
Deterministic Locks
Redis
Key-Value & Cache
Python
3.10, 3.11, 3.12, 3.13
Django
4.x, 5.x Frameworks
FastAPI
ASGI • Modern APIs
Next.js
React & Node Runtimes
Node.js
v20, v22 LTS
Docker
Compose & Containers
PostgreSQL
v14, v15, v16
Git
Repositories & Branches
uv & pip
Deterministic Locks
Redis
Key-Value & Cache
The Problem

“Works on my machine.”

Same codebase. Different runtime versions. Missing backing services. When environments diverge, identical code yields completely different realities.

commit a81f29cExact Same Code
Scroll into view to compare
A

Developer A

Author Machine • main@a81f29c

Evaluating...
Python Runtime:
3.12.10
Host OS:
Windows 11 (AMD64)
Django Framework:
5.1.2
PostgreSQL Database:
16.3 Active (Port 5432)
.env Configuration:
All 6 Variables Present
“Application boots with zero errors in 1.2s.”
B

Developer B

Teammate Machine • main@a81f29c

Evaluating...
Python Runtime:
3.11.9
Host OS:
Ubuntu 24.04 (Linux)
Django Framework:
5.1.2
PostgreSQL Database:
Not Installed / Inactive
.env Configuration:
DATABASE_URL Missing
“OperationalError: could not connect to server: Connection refused”
Different environmentsRunmarkA consistent understanding of what your code needs
How Runmark Works

From chaos to consistency.

Four deterministic steps to eliminate environment discrepancies and guarantee your code runs reliably everywhere.

01

Scan

Detect your environment

Inspect operating systems, runtimes, dependencies, services, and ports in milliseconds without daemons.

terminal — runmark scan
$ runmark scan
✓ Python 3.12.10 (AMD64)
✓ Node.js 22.19.0
✓ PostgreSQL 16.3 (Active)
Scan complete · 0.42s
02

Snapshot

Create a deterministic fingerprint

Compute a canonical SHA-256 fingerprint of your declared stack and store an immutable baseline snapshot.

snapshot — hashing engine
Hashing environment...
██████████████░░ 85%
SHA-256 fingerprint:
ce19840abda5675a...
Snapshot saved locally
03

Compare

Find discrepancies before failure

Detect semantic drift between developer machines, CI workers, and staging environments instantly.

diff — drift detection
Comparing against baseline...
Python ⚠ 3.12 vs 3.11
PostgreSQL ✕ Missing
Django ✓ 5.1.2 Match
2 discrepancies flagged
04

Verify

Guarantee compliance everywhere

Enforce contract compliance in pre-commit hooks and CI pipelines with standard exit codes and zero cloud bloat.

contract — verify check
Contract: runmark.json
Environment rules evaluated
Host compatibility verified
✓ PASS: 100% In Sync
Ready to boot application
01 Scan02 Snapshot03 Compare 04 Verify
Feature Highlights

Everything you need to understand your environment.

Explore all features

Environment Scanning

Runmark inspects host operating system facts, runtimes (Python, Node, Docker, Git), project signals (pyproject.toml, package.json, Dockerfile), declared/locked dependencies, background services (PostgreSQL, Redis), and port availability without mutating system state.

$ runmark scan

Smart Snapshots

Persist immutable environment snapshots into local atomic storage (`.runmark/snapshots/`). Every snapshot includes a deterministic SHA-256 fingerprint generated from canonicalized environment properties.

$ runmark snapshot -m "Initial dev baseline"

Drift Detection

Semantic diff engine that compares your live environment against a baseline snapshot or two snapshots against each other. Categorizes changes as ADDED, REMOVED, CHANGED, or UNCHANGED with rule-driven severity.

$ runmark diff
New

Environment Contracts

Declare required runtimes, dependencies, services, ports, container tools, and environment variable requirements in a version-controlled `runmark.json` file validated against formal JSON schemas.

$ runmark contract init --dry-run

Verification & CI Exit Codes

Evaluates the host machine against a verified snapshot or project contract, yielding standardized exit codes suitable for CI pipelines, pull request gates, and pre-commit hooks.

$ runmark verify --strict

Doctor / Diagnostics

Deep diagnostic engine that breaks down issues into concrete observed evidence, inferred reasoning, and clear read-only fix instructions to get developers back to coding quickly.

$ runmark doctor
READY
$
Real CLI Experience

See it in action.

A simple command gives you a clearer, deterministic picture of your development environment. No bloated daemons, no background cloud trackers.

Ready to scan
Sub-second execution
Scans runtimes, dependencies, and ports concurrently without daemon overhead.
Zero-Secret guarantee
Multi-pass heuristic credential masking guarantees 0 credentials leaked in snapshots.
Deterministic hashing
Identical environments always produce identical digests across host machines.
Interactive Simulation

See environment drift in action.

Test how Runmark detects discrepancies across Python, Django, Node, and background services in our browser simulator.

Drift Simulation Preview4 Differences
Python:3.12.10 → 3.11.9
OS Platform:Windows → Linux
Node.js:22.19.0 → 20.11.1
Django:5.1.2 (Match)
Latest Releasev0.2.2Aug 15, 2026

Contract Bootstrap & Developer Experience

Added evidence-driven contract synthesis (runmark contract init), live contract check cards (runmark check --explain), and pre-export canary security verification.