Email infrastructure, simplified

Good things start with a message.

The email relay for everything you're building. Bring your Postmark account, give each application a token, and get back to your product.

hello-world.sh

# Your first email. That's the whole request.

curl https://master.fabrica.g.combine.mesa.sh/api/v1/emails \
  -H "Authorization: Bearer $FABRICA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "to": "someone@example.com",
  "from": "hello@your.app",
  "subject": "You're in.",
  "text_body": "Let's make something good."
}'
→ 200 OK accepted by Postmark

Application-scoped tokens

One token per application, easy to rotate or pause.

Encrypted provider keys

Your Postmark server token is encrypted at rest.

A drop-in Elixir adapter

Keep composing mail with Swoosh, swap the adapter.

Ready to self-host

A small layer over your stack, yours to run.

How it works

From idea to inbox.

A shared home for your email infrastructure, with a clear boundary around every application.

01

Make a little space.

Organize a project, a business, or your next experiment. Your spaces belong to your Citadel identity.

02

Bring your Postmark key.

Connect email once per space. Fabrica encrypts the server token and shares the connection with your applications.

03

Ship the message.

Create an application, copy its token, and send through a simple HTTP API. Rotate or pause access whenever you need.

Made to fit your stack

A new token. The same mailer.

Using Elixir and Swoosh? Copy one adapter module, configure your Fabrica URL and token, and keep composing email the way you already do.

Meet the adapter →

config/runtime.exs

# One adapter. The same Swoosh mailer.
config :your_app, YourApp.Mailer,
  adapter: FabricaMail,
  base_url: "https://master.fabrica.g.combine.mesa.sh",
  token: System.fetch_env!("FABRICA_TOKEN")

Your next message starts here.

Sign in with Citadel. Your provider stays yours.

Sign in with Citadel