Membrane.

Simplify persistance

There's no need to connect a database (although you can!) because Membrane programs run in a durable JavaScript runtime.

That's right, we transparently persist memory changes so that you don't worry about loading and storing state.

Any JavaScript object can persist indefinitely because Membrane's execution timeout is effectively

Keep long-lived values in state.
import { state } from "membrane";
state.notes = state.notes ?? []
export async function saveNote({ args }) {
  state.notes.push(args.note);
}

Auditable

The most time-consuming part of bugfixing can often be reproducing the issue in the first place. We didn't like that, so we fixed it!

In Membrane, every side-effect is first written to the program's write-ahead log and then processed. HTTP requests and responses, source code changes, queries, etc are all program side-effects.

This log gives you clear understanding plus the ability to replay history so that reproducing bugs is a walk in the park.

Membrane logs are not just text output; they are the source of truth!

The Graph

In Membrane, each program defines a graph API to expose its data and functionality to other programs. You can think of the graph as objects that can be referenced by other programs, allowing you to easily compose functionality.

In this video we showcase the graph in a quick tour of the Membrane IDE.

Outgoing HTTP requests can be routed through an exit-node under your control. This is crucial when talking to APIs that implement IP-based rate limits, services behind a firewall, or to inject your own credentials privately.

Simply run mctl exit-node on any computer and Membrane will route all outgoing traffic through it while the command is running.

You can pass a script or program with --transformer. The script can modify or inject new headers. For example, inject an API key in the Authorization header. The script (or program) receives the request headers as JSON via stdin and outputs the modified headers in stdout.

Durable Programs ....................................................................................................0

Cron Jobs and Timers ....................................................................................................

Membrane Web IDE ....................................................................................................2

The Graph ....................................................................................................

Graph-based Access Control ....................................................................................................4

Observability ....................................................................................................

Instantanous Deploys ....................................................................................................6

Step Debugger ....................................................................................................

Custom Exit Nodes ....................................................................................................8

Simply run mctl exit-node on any computer and Membrane will route all outgoing traffic through it while the command is running.

HTTP Endpoints ....................................................................................................9

Open Source Drivers (APIs) ....................................................................................................10