The .git Developer Experience Manifesto

Our unwavering principles for building tools that respect your time, amplify your focus, and never get in the way.

Preamble

At .git, we believe developer tools should disappear into the workflow. Configuration should be optional, errors should be actionable, and deployments should feel instant. This manifesto isn't marketing copy—it's the contract we hold ourselves accountable to with every release, every API endpoint, and every line of CLI output.

We don't optimize for dashboard metrics or enterprise compliance forms first. We optimize for the terminal, the diff, and the developer's cognitive load.

Core Principles

  • 01 Developer Time is Non-Renewable

    We design for speed by default. Zero-config deployments, intelligent defaults, and automated retries. If it requires a manual workaround that takes more than 10 seconds, we've failed.

  • 02 Automation Over Ceremony

    Rituals in code are technical debt. We eliminate boilerplate, auto-detect frameworks, and generate pipelines from context. You write code, not infrastructure YAML.

  • 03 Transparency is Trust

    No black boxes. Every decision is logged, every rollback is traceable, and every failure includes a fix command. We publish uptime, latency, and incident post-mortems publicly.

  • 04 Standards Over Walled Gardens

    We build on open standards, not proprietary lock-in. Export your data. Migrate your state. Use standard Git workflows. Your code belongs to you, not our platform.

  • 05 Failure Should Be Fast & Forgiving

    Failures must be immediate, localized, and recoverable. We provide preview URLs for every PR, immutable deploy hashes, and one-command rollbacks. Breakage is a feature of growth—friction is not.

  • 06 Local First, Global Ready

    Your local environment is authoritative. We mirror production parity down to the CLI. Edge caching, CDN routing, and global replication happen silently after you commit.

  • 07 Feedback is a Feature

    Every CLI command, API response, and UI interaction must be debuggable. We surface telemetry opt-ins, structured logs, and actionable hints. Silence is the enemy of progress.

  • 08 Ship Often, Break Nothing

    Continuous delivery isn't optional. We test against real production traffic via canary analysis. Backwards compatibility is enforced at the compiler level, not the release notes.

Our Commitments to You

Principles are promises. Here's how we operationalize them:

🕒 Response Time SLA

API & CLI responses under 150ms p95. If we miss it, you get credits. No exceptions.

🔓 Data Portability

One-command export of all repos, configs, and build history. Open formats only.

🛡️ Zero-Knowledge Security

Secrets never touch our logs. Encryption keys are client-managed. Audit trails are append-only.

📈 Observable by Default

Every deployment generates OpenTelemetry-compatible traces. No SDK installation required.

How We Measure DX

We don't guess. We track:

  • Time-to-First-Commit: From repo creation to first successful push
  • Friction Index: Number of manual steps to achieve common workflows
  • Recovery Velocity: Mean time to rollback + redeploy after failure
  • CLI Exit Code Compliance: 100% POSIX-compatible error handling
$ .git dx-audit --env production # Running DX compliance check... # ✅ All 8 principles verified # 📊 Friction Index: 0.12 (target < 0.2) # 🔍 Report exported to ./dx-report.json

Contribute to the Manifesto

This document is version-controlled and open to pull requests. We welcome proposals, counterarguments, and real-world DX audits. If you ship software, your voice belongs here.

💡 Want to suggest a principle?

Open an issue in our public repo or run .git manifest draft to scaffold a proposal.