Monthly Downloads: 0
Programming language: JavaScript
License: MIT License
Tags: Content Management Systems (CMS)    
Latest version: v0.5.9

Expressa alternatives and similar software solutions

Based on the "Content Management Systems (CMS)" category.
Alternatively, view Expressa alternatives based on common mentions on social networks and blogs.

Do you think we are missing an alternative of Expressa or a related project?

Add another 'Content Management Systems (CMS)' Software solution


[](expressa.png) CircleCI

data-driven extendable API middleware for Node.js/Express

Expressa makes it easy to create basic APIs by using JSON schema:

  • django-like admin interface for creating collection-REST endpoints and managing permissions
  • collection schema's can be edited and added through the admin interface
  • re-use collection schema's in your frontend to generate forms
  • easily extendable so you can add complex features as well
  • define collections as JSON schema instead of custom code
  • per-collection database storage: MongoDB, PostgreSQL, or JSON-files (useful for version control)

Best of all: it's just middleware, not a framework

  • mix-and-mash: easily throw in other express middleware and endpoints
  • decorate expressa-endpoints: add event listeners which stop/modify requests (responses)

Getting Started

It's very easy to install expressa in your project directory:

mkdir myapp
cd myapp
npm init
npm install expressa express

Create a file app.js with the following code (or just copy the middle 3 lines into your existing express app)

var express = require('express');
var app = express();

var expressa = require('expressa');
app.use('/admin', expressa.admin({ apiurl: '/api/' }));
app.use('/api', expressa.api());

app.listen(3000, function () {
  console.log('Example app listening on port 3000!');

Now start the server by running node --use-strict app.js and navigate your browser to http://localhost:3000/admin/

API endpoints

Once you add a collections in the admin interface, every collection will have the following endpoints:

method endpoint description
POST /user/login expects JSON in the message body. e.g. `{"email": "[email protected]", password: ""}
GET /:collection get an array of all documents in a collection
GET /:collection/:id get a specific document
GET /:collection/?query={..} get an array of documents matching the mongo query. For pagination append &skip=0&offset=0&limit=6
GET /:collection/?query={..}&limit=10&page=1&orderby=["meta.created"] same as previous, but with pagination support
GET /:collection/?query={..}&limit=10&offset=10 same as previous, but with finergrained output control
GET /:collection/?query={..}&fields={..} the fields param can be used to do a mongo projection to request only specific fields
GET /:collection/?fieldname=value get an array of documents matching with the specified values. See node-mongo-querystring for details.
GET /:collection/schema get the collection schema
POST /:collection/ create a new document, the message body should be the JSON document
PUT /:collection/:id replace the document with id. The message body should be the JSON document. If the _id in document is different (the old document _id is deleted and a new one with id is created.)
POST /:collection/:id/update modify the document with id using a mongo update query. The message body should be the update query
DELETE /:collection/:id delete the document

Supported Data: Only standard JSON (strings, numbers, booleans, null) is supported. Dates can be stored as strings using ISO 8601


  • Requests
    • [Querying](doc/querying.md)
    • [Making authenticated requests](doc/authentication.md)
    • [Pagination and sorting](doc/querying.md)
  • Collections
    • [Automatic fields](doc/automatic-fields.md)
  • Server-side implementation
    • [Modifying behavior using listeners](doc/listeners.md)
    • [Adding custom endpoints](doc/custom-endpoints.md)
    • [Accessing the database](doc/database.md)
  • Admin Panel
    • [Relationships](doc/relationships.md)
    • [Permissions](doc/permissions.md)
    • [Uploading files](doc/uploading-files.md)
  • [Testing / CI integrating your expressa app](doc/testing.md)

Folder Structure

The Expressa configuration is in a folder called "data" in your project. There is a subfolder for the collections that you choose to persist to disk. By default, the following will be added once you finish the installation.

folder purpose
data/settings Config file per environment. Can include custom variables specific to your project.
data/role List of roles in the permission system. Defaults to "Admin", "Anonymous" and "Authenticated".
data/collection JSON Schemas and settings for each collection.

Note: The files in these data folders are JSON so they can be manually updated or you can edit them in the Admin UI. Generally these files should be checked into version control.

Admin UI Examples/Screenshots

  • [Example: Creating a blog collection and post in the UI](doc/blogexample.md)
  • [Managing CRUD permissions in the UI](doc/permissions.md)

Expressa ecosystem

  • expressa-folder easily extend expressa collections with ORM-ish js-code (get.js/post.js/functions.js/etc) & setup sub-endpoints
  • expressa-swagger middleware to generate online api documentation
  • expressa-client middleware to generate browser REST-client (+nodejs client)
  • expressa-cli commandline interface for expressa


  • Automatic GraphQL Support
  • JWT token expiration
  • Support cookie based authentication as well
  • File uploads


Expressa is not primarily built for simple blog websites or mostly static content websites. For those a cms like Keystone.js and enduro.js could work or maybe you could build you site with a static site generator like Hugo. For database-driven websites that need a strong CRUD backend where you want a clear separation between the frontend and backend, expressa.js is a great choice.


Version Important Changes
0.5.3 Fixes bug in install where enforce permissions wasn't activated. Fixes CSV download.
0.5.2 Fixes bug when installing super user in Admin tool
0.5.1 Includes built Admin UI in npm package
0.5.0 Migrates server to use async/await. New Admin UI built with Vue.js. Adds request-id headers
0.4.6 Fix some errors in the install process when choosing to store users in mongo or postgres
0.4.5 Security update
0.4.1 db.create (postgres) now returns the id instead of the full document.
0.4.0 Pagination now starts with page 1. Delete requests can no longer bypass rejections by listeners. Updated permission error codes/messages. Error responses now always json (with an "error" field explaining) PUT /collection/:id response changed to match POST /collection
0.3.3 Fixes security vulnerability with the "edit own" permission and the :collection/:id/update endpoint. Update immediately.
0.3.2 Pagination is now supported by specifying the "page" and "limit"
0.3.1 Makes "development" the default settings file instead of "production". Use NODE_ENV environmental variable to change this. To quickly migrate, just rename your settings file to "development".

Inspired by