# Parity > Parity runs Citadel's own PHP image, Citadel's proxy and MySQL 5.6 on your Windows, macOS or Linux computer, so an app that works locally works on Citadel. One program, one parity.json, no PHP needed. **Run Citadel on your own computer.** Citadel's PHP image, Citadel's proxy and MySQL 5.6, on your laptop, so an app that works here works on Citadel. "Works on my machine" finally means something, because your machine is now Citadel's twin. Parity is one program, `parity`, for Windows, macOS and Linux (x64 and arm64). It needs a container engine, Podman Desktop (recommended, free) or Docker Desktop if you already have it, and nothing else: no PHP, no Composer, no files in your app beyond one `parity.json`. `parity check` also knows the other engines people already run (see [Docker or Podman](#docker-or-podman)). > Parity is a mirror, not a portrait: it shows Citadel as Citadel is, including the parts you would rather it did not. Every page below is Markdown. The HTML pages send the same Markdown to a client that asks for `text/markdown`. Written by Squire's agent-ready kit from the README and the pages; do not edit. ## Pages - [Parity: Run Citadel on your own computer.](https://parity.apps.wayne.edu/index.md): Parity runs Citadel's own PHP image, Citadel's proxy and MySQL 5.6 on your Windows, macOS or Linux computer, so an app that works locally works on Citadel. One program, one parity.json, no PHP needed. - [Changelog | Parity docs](https://parity.apps.wayne.edu/docs/changelog.md): All notable changes to this project. - [FAQ | Parity docs](https://parity.apps.wayne.edu/docs/faq.md): Short answers to the questions people ask first about Parity, from PHP on the laptop to Oracle, HTTPS and CI. - [The desktop app (after 1.0) | Parity docs](https://parity.apps.wayne.edu/docs/guides/desktop-app.md): Parity's desktop app, coming after 1.0 and not released yet. The same Go code as the parity command, as one window, with screens from the work in progress. - [Coming from Squire's parity kit | Parity docs](https://parity.apps.wayne.edu/docs/guides/from-squire.md): Move an app from Squire's parity kit (squire init --only=parity) to Parity, what carries over, what stays behind, and what to expect to differ. - [How Parity works | Parity docs](https://parity.apps.wayne.edu/docs/guides/how-it-works.md): The three containers parity up starts, mount and bake, what lands in .parity/, and how the output changes between a terminal and a CI log. - [Citadel's images | Parity docs](https://parity.apps.wayne.edu/docs/guides/images.md): The images Parity knows, the three ways parity image get downloads one, what "matches Citadel" checks, and what happens when Citadel has not published an image yet. - [Parity | Parity docs](https://parity.apps.wayne.edu/docs/index.md): What Parity is, what it needs, and the five commands that take an app from nothing to running the way Citadel runs it. - [Install | Parity docs](https://parity.apps.wayne.edu/docs/install.md): Install Parity on Windows, macOS or Linux with one line, take a download yourself, or build it from source. - [Commands | Parity docs](https://parity.apps.wayne.edu/docs/reference/commands.md): Every parity command and option, from the program's own help, with exit codes and the environment variables it reads. - [parity.json | Parity docs](https://parity.apps.wayne.edu/docs/reference/parity-json.md): Every field of parity.json, the one file Parity adds to an app, with the Citadel setting each one mirrors and its default. - [Troubleshooting | Parity docs](https://parity.apps.wayne.edu/docs/troubleshooting.md): The findings parity check reports most often, what each means and how to fix it, from container engines and WSL 2 to line endings, ports and arm64. ## Prompts - [Get started with Parity](https://parity.apps.wayne.edu/#prompt-get-started): Checks the computer, writes parity.json, brings the app up on Citadel's image and smoke tests it. It asks before changing anything outside the app. The prompt itself is in https://parity.apps.wayne.edu/index.md. - [Move from Squire's parity kit](https://parity.apps.wayne.edu/#prompt-from-squire): Carries the kit's settings into parity.json, proves the app comes up on Parity, and leaves the kit's files for you to remove. The prompt itself is in https://parity.apps.wayne.edu/index.md. ## Source - [README](https://git.wayne.edu/enterprise-apps/parity/blob/HEAD/README.md): the project's README, with install, commands and checks - [Everything in one file](https://parity.apps.wayne.edu/llms-full.txt): the README and every page above, as one Markdown file ## Optional - [ADVISOR](https://advisor.apps.wayne.edu/llms.txt): the stack's MCP server: read-only tools that answer from CREED's policy and the parts' docs instead of from memory - [WELD](https://weld.apps.wayne.edu/llms.txt): the Wayne State application stack: every part, and the reference app