dxup - Reproducible Environments from Dev to Production

_ | | __| |_ ___ _ _ __ / _` \ \/ / | | | '_ \ | (_| |> <| |_| | |_) | \__,_/_/\_\\__,_| .__/ | | |_|

Ship with confidence. Same environment everywhere.

Same setup, every time. Development to production. Zero config.

Built on Docker + Nix. AGPL v3 licensed.

dxup.sh

# New developer onboarding: 3 seconds

$ git clone github.com/mycompany/webapp && cd webapp

$ dxup up

✓ Ready to code · no manual setup required

How It Works

dxup combines battle-tested technologies into a single, simple CLI. Use CLI commands to define your stack—dxup generates everything behind the scenes. No config files to write, no Kubernetes learning curve, no Docker expertise required.

✓ Nix for bit-perfect reproducibility

✓ Docker for isolation & consistency

✓ Swarm for simple orchestration

Same environment everywhere: localhost, CI, staging, production. No drift. No surprises.

Get Early Access

Be first to know when Team & Enterprise features launch

Open source will always be free. This is for commercial features only.

★ Star on GitHub

AGPL v3 licensed · Open source

Get Started

1
Clone the repository
git clone https://github.com/dxupsh/dxup.git
2
Follow the setup instructions in the README

                Questions? Open an issue on GitHub.
            

Real Problems. Real Solutions.

Every team faces these challenges. See how dxup solves them.

Problem

Every new hire means hours of manual setup: installing tools, fixing version mismatches, debugging OS-specific failures. Your team repeats this ritual with each person who joins. First day productivity? Zero. Average setup time: 3-4 days, costing ~$2,000 in lost productivity per hire.

dxup

New developers clone and run one command. Nix guarantees their environment matches everyone else's—bit-for-bit identical. No installation guides, no troubleshooting, no waiting. They're writing code within minutes, not days. Unlike manual Docker Compose setups, dxup ensures zero configuration drift across your entire team.

Problem

Code passes all tests. You deploy to production. Then: a 3am alert. Something broke—but it works perfectly on your laptop. Days spent hunting down environment differences instead of shipping features. Each incident: 2+ hours debugging, plus customer impact and lost revenue.

dxup

Your entire stack—every dependency, version, and configuration—is declared once via simple CLI commands. Development, CI, staging, production: identical environment, guaranteed by Nix reproducibility. Docker Swarm ensures the same orchestration in production that you use locally. Environment drift becomes impossible. Deploy with confidence.

Problem

Modern development means mastering orchestration tools, container runtimes, networking configs. Your developers spend 40% of their first week on setup, not features. Docker Compose is great for single machines, but scaling to teams and production means learning Kubernetes or maintaining complex deployment scripts. Everyone becomes a part-time DevOps engineer.

dxup

Define your stack with simple CLI commands. dxup handles the complexity—Nix for reproducibility, Docker for isolation, Swarm for orchestration—behind the scenes. No config files to write, no Kubernetes YAML, no Docker expertise needed. Developers run two commands: dxup up to start coding, dxup deploy to ship. Zero infrastructure expertise required.

Frequently Asked Questions

How is dxup different from Docker Compose? ▶

Docker Compose is great for local development, but doesn't guarantee consistency across teams or to production. dxup uses Nix to ensure bit-perfect reproducibility, Docker for isolation, and Swarm for production-grade orchestration—all managed through simple CLI commands. No YAML files to write or maintain. Think of it as "Docker Compose, but it actually works the same everywhere."

Will this work with my existing stack? ▶

dxup supports common languages and frameworks out of the box: Node.js, Python, Go, Rust, Ruby, and most databases (Postgres, MySQL, Redis, MongoDB). If your stack runs in Docker, dxup can handle it. Add services using simple CLI commands—no config files needed.

Do my developers need to know Docker or Kubernetes? ▶

No. dxup abstracts away the complexity. Developers only need to know two commands: dxup up to start and dxup down to stop. Behind the scenes, dxup manages Docker containers and Swarm orchestration automatically.

How does dxup handle production deployments? ▶

dxup uses Docker Swarm for orchestration, which is simpler than Kubernetes but still production-ready. Your same environment deploys to production with dxup deploy. For most teams (95%), Swarm provides the orchestration you need without the Kubernetes learning curve.

What if I'm already using Kubernetes? ▶

If you're already invested in Kubernetes, dxup may not be for you—and that's okay. dxup is designed for teams that want production-grade orchestration without the Kubernetes complexity. However, you can still use dxup for local development and keep K8s for production.

Is dxup free and open source? ▶

Yes. dxup is completely free and open source under the AGPL v3 license. The full CLI and all core features are available on GitHub for anyone to use, modify, and contribute to.

Built By Engineers, For Engineers

dxup was created by developers who've spent too many hours debugging "works on my machine" problems in production systems. We built the tool we wished existed: simple, reliable, and focused on solving real problems—not chasing VC-backed hype. No enterprise sales pitch, just practical solutions for teams that want to ship code with confidence.