With the winding down of the Parse hosted service and the transition to the Open Source Parse Server, many of you have been asking how you will manage your app when it’s running on your own system. Today we are answering that question with Parse Dashboard. You can start using it today to manage the apps that you have already moved to Parse Server, your apps that are still on Parse.com, and your apps that are still in development and running on Parse Server on your development machine. You can even manage them all from the same dashboard.

Getting Started

The Parse Dashboard is adapted from the same dashboard we launched in December, and running it will feel very familiar to any Node.js or web developers. If you already have Node.js, all it takes to get started is four simple commands to clone the source code, and a little bit of info in a config file.

git clone [email protected]:ParsePlatform/parse-dashboard.git
cd parse-dashboard
npm install

Now that you have the dashboard installed, edit the parse-dashboard-config.json file in the Parse-Dashboard folder, and add your app’s ID, master key, server URL, and name, like this file:

  "apps": [
      "serverURL": "http://localhost:1337/parse",
      "appId": "myAppId",
      "masterKey": "myMasterKey",
      "appName": "MyApp"

Then, execute npm run dashboard and visit http://localhost:4040 in your browser, and you will see your app! For your apps on Parse.com, you can currently use the Data Browser, edit your Parse Config, use the API console, and view your Cloud Code and logs. For apps on Parse Server, the Data Browser and API console are available.

Parse Dashboard Screenshot

Staying Up to Date

The Parse Dashboard detects which features are available on your Parse Server and enables only the features that are actually available. This makes it very easy to keep your dashboard up to date with the latest and greatest with just git pull, even if your apps on Parse Server aren’t yet using the latest version.


Having the Parse Dashboard be a completely separate project from the server also makes it easy to add new features to the dashboard and have them available immediately. We hope to see the Parse community take ownership of the Parse Dashboard and drive the creation of new features and distribution methods. Many of the features from Parse.com can be supported with only some small tweaks, so we’ve made all of the code for the dashboard available, even for features that currently aren’t available in Parse Server. Happy hacking!

Drew Gross