DevContract uses SSH key conversion and three-way merges to sync environment variables

A local-first, peer-to-peer Go CLI that replaces centralized secret managers with direct LAN sync, operator-opaque relays, and git-style conflict resolution.

DevContract is built for small, engineering-heavy teams that want to share .env files without trusting a centralized SaaS provider like Doppler or 1Password. By deriving transport keys from existing SSH identities and running three-way merges on environment changes, it solves the dual problem of key distribution and clobbered local configurations. Skip it if your team lacks terminal comfort or requires complex enterprise access control policies. For small teams, it is a highly secure, zero-overhead alternative to copy-pasting secrets over Slack.

Methodology

This v0 review draws on the technical design and source code published by founder Dan Twoashim on GitHub (dantwoashim/DevContract) as of May 2026. Independent cryptographic audits and performance benchmarks are pending. We analyzed the Go implementation details, specifically the curve conversion math, the mDNS discovery implementation, and the three-way merge state machine. This review covers the architectural feasibility of the peer-to-peer sync engine and the local validation contract. It does not cover long-term reliability under high-latency network conditions, edge cases in the three-way merge algorithm, or security vulnerabilities in the custom Noise-protocol handshake implementation. We will update this review once we run a multi-node test rig.

What it does

Identity derived from SSH keys

Instead of requiring user accounts, DevContract reads the user's local ~/.ssh/id_ed25519 key. It performs a birational map conversion (Edwards-to-Montgomery curve mapping) to derive X25519 transport keys from the Ed25519 signing key. This allows secure key exchange without a central registry.

Peer-to-peer local synchronization

When teammates are on the same local network, the CLI uses mDNS to discover peers. It establishes a direct Noise-protocol TCP socket to sync secrets peer-to-peer. No data leaves the local area network during these syncs.

Stateless relay fallback

For remote or offline sync, DevContract encrypts payloads locally using XChaCha20-Poly1305. It binds the ephemeral public key as associated authenticated data (AAD) to prevent key-substitution attacks and pads the plaintext to a 1KB boundary. The encrypted payload is queued on a stateless Cloudflare Worker backed by Durable Objects.

Lineage-based three-way merges

Unlike standard secret managers that rely on last-write-wins, DevContract tracks parent lineage for environment variables. When pulling changes, it performs a three-way merge based on a common local ancestor, auto-merging non-overlapping changes and flagging conflicts.

Local contract validation

A local contract.yaml file defines required backing services, such as Postgres or Redis ports. The CLI validates that these dependencies are running locally before pulling down the environment keys.

What's interesting and what's not

The good: Git-style merges for secrets

The three-way merge engine is a major improvement over the last-write-wins strategy used by Doppler and 1Password. In teams where developers frequently modify local configurations, last-write-wins inevitably clobbers custom local variables. By tracking lineage, DevContract treats environment variables like code, allowing clean merges. The SSH key derivation is also elegant, eliminating the need to manage another set of credentials.

The bad: The relay is still a central point

While the relay is operator-opaque and cryptographically secure, it still introduces a centralized infrastructure dependency (Cloudflare Workers) for remote teams. If the relay is down, out-of-office sync fails. Additionally, the reliance on mDNS for local discovery can be brittle on enterprise Wi-Fi networks that block multicast traffic. The tool also lacks a robust access control mechanism. Anyone with access to the repository's SSH keys can theoretically write to the environment, which may not scale past small, trusted teams.

Pricing

DevContract is open-source and self-hosted. There are no licensing fees or SaaS tiers as of May 2026. Users must deploy their own Cloudflare Worker relay if they require remote sync capabilities, which fits within Cloudflare's free tier limits for small teams.

Verdict

DevContract is a compelling choice for small, technical teams that value local-first architecture and want to avoid SaaS lock-in for secret management. Its three-way merge engine solves the real pain of clobbered local configurations, and its SSH-based identity derivation is a masterclass in zero-trust design. However, larger organizations that require fine-grained access control, audit logs, or SAML integration should stick to enterprise managers like Doppler or HashiCorp Vault. DevContract is a developer's tool built for speed and security on small teams.

What we'd test next

In our next phase of testing, we want to benchmark the three-way merge engine against complex, conflicting environment changes to see how gracefully it handles edge cases. We also plan to test the mDNS discovery reliability across different router configurations and corporate VPNs. Finally, we will audit the Go implementation of the Edwards-to-Montgomery curve mapping to ensure there are no side-channel leaks or edge-case failures during key derivation.

The investor read

DevContract represents a growing developer backlash against centralized, high-margin SaaS security tools like Doppler and 1Password. While enterprise buyers prioritize compliance, auditability, and centralized access control (which keeps Doppler highly investable), early-stage engineering teams are increasingly seeking zero-trust, local-first alternatives that eliminate recurring subscription costs and external database dependencies. DevContract itself is a bootstrapped, open-source utility rather than a venture-scale business. However, its architecture signals a shift: security tooling is moving toward infrastructure-derived identity (like SSH keys) and peer-to-peer synchronization. Investors should watch for commercial platforms that can wrap this local-first, zero-trust developer experience in an enterprise-compliant management plane.

Pull quote: “The three-way merge engine is a major improvement over the last-write-wins strategy used by Doppler and 1Password.”