Local-first email production

Your email workspace,
without the friction.

A small, reliable bridge between your local files and the Stripo editor. Build confidently, keep your credentials private, and pick up where you left off.

* Community project, not affiliated with Stripo.

Designed for local development
editor.stripo.email
HTML Design Saved
make
something
useful
Scroll to explore

The simple version

One workspace.
Three useful moves.

01

Open the editor

Start the local server and launch a fresh Stripo session in your browser.

Read the setup
03

Save and reopen

Keep HTML and CSS together in a local template file, ready for the next session.

See the lifecycle

Made for focused email work

Know when
it fits.

Use the local development kit when your email work needs a clear path from visual design to local, reusable project files.

Email designers

Build campaigns in Stripo while keeping each project organized and easy to revisit.

Frontend developers

Keep HTML, CSS, and project history close to the rest of your local development workflow.

Small teams

Share a predictable setup and preserve work between people, sessions, and iterations.

Before the first click

Set the stage
in four steps.

Everything runs locally. You bring the Stripo credentials; the dev kit takes care of the handoff.

You will need Node.js 18+, npm, Git, a Plugin ID, and a Secret Key.
01

Download the project

Clone the repository , then move into the local-stripo-api directory.

02

Make private settings

Copy .env.example to .env and add your Stripo Plugin ID and Secret Key.

03

Install dependencies

Run npm install once from the project directory.

04

Start the app

Run npm start, then open http://localhost:3000.

Your project, your files

Keep the thread
between sessions.

The editor is where you design. Your filesystem is where your work stays legible, portable, and yours.

<parent-directory> / <project-name> template.json · HTML · CSS
Design Work in the Stripo editor
Save Write HTML and CSS locally
Reopen Pick a project and continue

A good boundary

Private by
default.

Your Secret Key stays on the server. It never belongs in browser code, and .env should never be committed to GitHub.

Secret stays server-side Credentials live in .env Add auth before going public