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.

Membrane programs cannot make network requests or access your graph unless they are explicitly given access to the right nodes. You're in complete control of which programs can access what.

Even the standard fetch function is implemented in terms of graph nodes. It's through the graph that programs make HTTP requests, send emails, access APIs, and so on.

The graph ensures that programs, including those you didn't write, only execute their intended functions and nothing more. It is how programs communicate with each other and the outside world.

The graph is explorable and typed. Anything is referenceable so access to data can be very fine-grained. We like to think of it as a capability-based access control model.

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

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

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

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

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

Membrane programs cannot make network requests or access your graph unless they are explicitly given access to the right nodes. You're in complete control of which programs can access what.

Even the standard fetch function is implemented in terms of graph nodes. It's through the graph that programs make HTTP requests, send emails, access APIs, and so on.

The graph ensures that programs, including those you didn't write, only execute their intended functions and nothing more. It is how programs communicate with each other and the outside world.

The graph is explorable and typed. Anything is referenceable so access to data can be very fine-grained. We like to think of it as a capability-based access control model.

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

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

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

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

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

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

Code completion ....................................................................................................

Github Action Alert ....................................................................................................0

SMS Reminders ....................................................................................................

Mailchimp Alerts ....................................................................................................2

Follow Hacker News Users ....................................................................................................3

Airtable changes to Email ....................................................................................................4