# Automattic/wp-calypso: Running the WordPress.com Admin Locally

> Calypso is the React and Redux front end for WordPress.com, backed by the WordPress.com REST API. It is a monorepo you can clone and run on port 3000, and it has not received a push since 2021-06-02.

**Automattic/wp-calypso** — The JavaScript and API powered WordPress.com

- Repository: https://github.com/Automattic/wp-calypso
- Website: https://developer.wordpress.com
- Stars: 12,647 · Forks: 2,029
- Language: TypeScript
- License: GPL-2.0
- Published: 2026-08-21 · Updated: 2026-08-21 · Language: en
- Canonical page: https://hysenlabs.com/projects/automattic-wp-calypso

## The WordPress.com dashboard, rebuilt as a single-page app

Calypso is the front end that WordPress.com serves to logged-in users. The README describes it as "a beautiful redesign of the WordPress dashboard using a single-page web application, powered by the WordPress.com REST API", built for reading, writing and managing WordPress sites in one place. The problem it addresses is the one every legacy PHP admin eventually hits: a server-rendered dashboard that reloads the page for every action. Calypso replaces that with a client-side application that fetches data over the REST API and keeps state in the browser.

The audience is narrow and specific. It is not a plugin you drop into a self-hosted site. It is the codebase Automattic ships to WordPress.com, plus a local development environment for people who want to work on that codebase. If you run your own WordPress install, Calypso is not your admin; wp-admin still is. The README is explicit that the user-facing side lives on WordPress.com, and that cloning the repository is for poking around or running it locally.

## A Yarn workspace monorepo over the WordPress.com REST API

The architecture is visible in the repository layout. The root package.json declares Yarn workspaces covering client, desktop, apps/*, packages/* and test/e2e, and the package itself is private, with the description "A pure REST-API and JS based version of the WordPress.com admin". The README names the front-end stack directly: a light Node plus Express server, React.js, Redux, wpcom.js, and other libraries.

So the data flow is: React components render UI, Redux holds application state, wpcom.js is the client that speaks to the WordPress.com REST API, and a thin Express server serves the bundle and handles the pieces that cannot live in the browser. The desktop directory and its own release history (the v6.15.0 line is tagged as WP-Desktop) show the same codebase also packaged as a desktop application. The Dockerfile confirms the build shape: a dedicated dependency-install stage that copies only manifests and the lockfile first so the slow yarn install can be cached, followed by build stages, with environment flags such as SKIP_TSC, SKIP_CALYPSO_POSTINSTALL and SKIP_CALYPSO_PACKAGE_BUILDS used to skip work that is not needed for a given image.

## Installing Calypso and opening it on calypso.localhost:3000

The README gives a five-step path. You need git, node and yarn installed first. Clone the repository, then add a hosts entry so the app is reachable under its own hostname rather than localhost:

```bash
127.0.0.1 calypso.localhost
```

Then install dependencies and start the development server from the repository root:

```bash
yarn
yarn start
```

Finally, open the app in a browser at calypso.localhost:3000. That port is the one the README specifies, and the hosts entry is required rather than optional; the README lists it as step three, before the install command. The README points to docs/install.md for more detailed instructions and to docs/troubleshooting.md for the most common issues, which is where you should look first if yarn start fails.

One thing to verify before you run anything: the engines field in package.json requires Node ^v24.15.0 and Yarn ^4.0.0, while the last push to the repository was on 2021-06-02. Those two facts sit awkwardly together, and the repository files do not explain how the engines constraint and the older toolchain reconcile. Treat the engines field as the current statement of what the project expects, and check your local versions against it.

## Where Calypso is the wrong tool

The clearest limitation is scope. Calypso is the WordPress.com front end. If you administer a self-hosted WordPress site, installing Calypso gives you a client that talks to the WordPress.com REST API, not an interface to your own installation's database or plugins. Nothing in the README suggests a supported path for pointing Calypso at an arbitrary self-hosted site.

The second limitation is maintenance. The last push to the repository was on 2021-06-02, more than six months before today, so this is not a codebase being actively developed on the public trunk. The most recent releases are all WP-Desktop builds from the same period, and the v6.15.0 note reads "updater redirect to wp-desktop repository", which indicates that the desktop line moved elsewhere. Anyone cloning the repository today inherits a dependency graph frozen at that point, and the practical consequence is that a fresh yarn install may surface version conflicts that nobody is fixing upstream in this repository.

A third constraint is the supported environment. The README states browser support as the latest two versions of all major browsers, and the browserslist configuration in package.json has separate targets for wpcom, evergreen, server and test. There is no documented support for older browsers, and no compatibility layer described for them.

## How Calypso differs from WP-CLI and from wp-admin

The obvious comparison for anyone administering WordPress is WP-CLI, and the two solve different problems. WP-CLI is a command-line interface: you run commands against a WordPress installation on a server, and the output is text. Calypso is a graphical single-page application that talks to a remote REST API, and its output is a rendered interface. If your task is scripting a bulk operation, WP-CLI is the right shape. If your task is understanding how a modern React and Redux client consumes the WordPress.com REST API, Calypso is the relevant codebase.

The other comparison is wp-admin itself. wp-admin is server-rendered PHP inside the WordPress installation; Calypso is a separate JavaScript application that treats the API as its only data source. That separation is what makes Calypso portable across sites managed in one WordPress.com account, and it is also what makes it useless as a drop-in replacement for a self-hosted admin.

## Licence and the cost of keeping a fork alive

Calypso is licensed under GPL-2.0-or-later. The LICENSE.md file in the repository root carries the full text, and package.json states the same identifier. The practical implication of a copyleft licence at this scale is that if you distribute a modified version of Calypso, you take on the obligations that come with it. That is a general property of the licence, not advice about your situation; read LICENSE.md and, if the distinction matters to your organisation, get proper counsel.

The upgrade cost is the more immediate concern. Because the last push was on 2021-06-02, a fork today starts from a snapshot with no upstream fixes arriving on this branch. You would own dependency updates, security patches to the Node and Express layers, and any breakage from the WordPress.com REST API evolving underneath a client that is no longer being updated here. The Dockerfile's cache-seed mechanism, which pulls a prebuilt image from an internal registry, is another piece you would have to replace or reproduce, since that registry is not something an outside user can pull from.

## Conclusion

Adopt Calypso if you are working on the WordPress.com front end itself, or if you want a working reference for a REST-API-driven admin built with React, Redux and wpcom.js. Do not adopt it as the admin for a self-hosted WordPress site: it talks to the WordPress.com REST API, not to a site's own wp-admin, and the repository has not been pushed to since 2021-06-02, so its dependency graph reflects a much older Node and Yarn toolchain than the engines field now claims. Before you invest time, check that your Node and Yarn versions satisfy the engines field, read docs/install.md for the current setup path, and confirm the hosts entry for calypso.localhost resolves on your machine.

## FAQ

### What is Calypso used for?

It is the WordPress.com front end: a single-page application for reading, writing and managing WordPress sites, powered by the WordPress.com REST API. The repository is also the local development environment for working on that front end.

### What is the Calypso program?

The README describes Calypso as a redesign of the WordPress dashboard built as a single-page web application. It is built with a light Node and Express server plus React.js, Redux and wpcom.js on the front end.

### What is the latest version of Calypso?

The most recent release listed is v6.15.0, tagged as WP-Desktop 6.15.0 with the note "updater redirect to wp-desktop repository". The root package.json carries version 18.13.0, which is the workspace version rather than a release tag.

## Sources

- [Official documentation](https://developer.wordpress.com)
- [Official README](https://github.com/Automattic/wp-calypso#readme)
- [Project repository](https://github.com/Automattic/wp-calypso)
- [Release notes](https://github.com/Automattic/wp-calypso/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/automattic-wp-calypso