Oxamp

Native Apple Silicon PHP stack with AI agent safety

Visit Website
September 6, 2026 I built OXAMP because my Mac sounded like a jet engine running simple PHP sites

I love coding on Apple Silicon, but my local PHP stack was killing my productivity.

Every time I ran a basic WordPress or Laravel site, my Mac’s fans would roar. Legacy tools like MAMP feel stuck in the x86 era, and running Docker Desktop just for a simple local database felt like overkill—draining my RAM and battery in minutes.

So I built OXAMP: a lightweight, native arm64 web stack built from scratch in Swift and Rust.

The Big Fixes:

  • Native Speed: Apache, MariaDB, and PHP compiled strictly for Apple Silicon—boots instantly with zero Docker bloat.

  • AI Agent Protection: Since I use Cursor and Claude Code daily, I added built-in MCP guardrails so AI assistants can manage databases safely without accidentally dropping tables or wiping local settings.

  • No Subscriptions: 1-click WordPress/Laravel setups and dual-PHP switching for a one-time $29 fee.

I’m prepping for a broader launch and would love to know: How do you handle local PHP dev on Mac, and are you letting AI agents touch your local environments yet?

You can also visit the main website page for more information and review it - Oxamp

3 Comments

  1. 1
    The performance problem sounds concrete, but what evidence would make you confident developers will replace their current MAMP/Docker setup with OXAMP rather than just try it alongside?
    1. 1
      Totally fair point! To be honest, I don't expect anyone to just delete MAMP or Docker on day one, trying it alongside their existing setup is usually how it starts. From what I've seen, the permanent switch happens when two things sink in: Resource exhaustion: You keep Docker off for a whole day while coding, and your Mac stays completely cool while saving a ton of RAM and battery. Once you experience that native speed again, it's hard to go back to heavy containers for simple PHP work. AI coding safety: If you're using Claude Code or Cursor, running them against a raw MAMP or Docker setup can be sketchy. OXAMP has built-in MCP guardrails, so the AI can manage the environment without risking dropping local tables or messing up configs. For small to mid-sized projects, Docker is often overkill. When devs realize they get the same workflow in a lightweight, AI-safe native stack, OXAMP naturally ends up replacing their daily setup.
      1. 1

        That’s a much clearer replacement thesis, especially around resource usage and AI-assisted workflows. I’d be interested in digging into what users actually do after trying it. If you’re open to it, what’s the best email to reach you on?

About

Legacy stacks like MAMP/XAMPP are outdated, and Docker drains Mac battery. I built OXAMP natively for Apple Silicon with AI guardrails so devs can code safely and instantly.