• A Local Relay Changes How You Build
• What a Local Relay Actually Is
• Pubkey Whitelisting
• Docker Makes This Easy
• Why This Matters
• The Bigger Picture
• Work With Me
  • Early Adopters

Andrew G. Stanton - Sunday, March 8, 2026

Most Nostr developers spend their time interacting with public relays.

They publish events.
They read events.
They hope those relays behave consistently.

But public relays are outside your control.

They can:

• reject events
• go offline
• throttle connections
• filter content
• respond unpredictably

For everyday usage that is acceptable.

For development it can be frustrating.

That’s why one of the most useful things a Nostr developer can do is run a relay locally.

§A Local Relay Changes How You Build

When a relay runs on your own machine, several things immediately improve.

First, publishing becomes deterministic.

If your code publishes an event, you can verify exactly what happened because you control the relay receiving it.

Second, debugging becomes dramatically easier.

Instead of wondering whether a public relay dropped your event, you can inspect the relay database directly.

Third, development becomes faster.

Local relays eliminate network delays and remove a whole class of unpredictable behaviors.

§What a Local Relay Actually Is

Right now my relay runs locally inside Docker on my development machine.

It is not yet a permanent public relay.

Events written to it exist only on my machine unless they are also published to external relays.

In that sense it currently behaves more like a development relay.

But that is exactly what makes it useful.

It provides a controlled environment where I can test:

• event publishing
• relay responses
• delete events
• identity switching
• relay manager logic

Without depending on external infrastructure.

§Pubkey Whitelisting

One of the first configurations I enabled was pubkey whitelisting.

The relay accepts writes only from specific public keys.

This prevents spam and ensures that only approved identities can publish events.

For personal relays this is often a very practical configuration.

It turns the relay into a trusted publishing endpoint rather than a public write target.

§Docker Makes This Easy

Running the relay inside Docker keeps the setup portable.

The container can run locally during development and later move to another machine with minimal changes.

Eventually the same configuration could run on a small always-on machine and be exposed publicly at a domain like:

wss://relay.continuum.xyz

For now, though, it remains a development relay.

And that is perfectly fine.

§Why This Matters

Running a local relay deepens your understanding of how Nostr actually works.

You begin to see:

• how events are stored
• how relays handle writes
• how publishing logic should behave
• where failures actually occur

It also encourages a local-first architecture.

Instead of relying entirely on external infrastructure, you begin building systems that work locally first and connect outward second.

§The Bigger Picture

The long-term vision for many Nostr applications includes:

• local signing
• local archives
• local relay infrastructure
• optional replication to public relays

Running a local relay is a small step in that direction.

Even if it never becomes a permanent public relay, the benefits during development are significant.

And once you have one running, it becomes very clear why more Nostr developers should do the same.

§Work With Me

If you’re exploring:

• Nostr authentication
• Sovereign identity infrastructure
• AI-assisted workflows
• Local-first containerized systems

I offer a limited number of advisory and implementation sessions for builders, teams, and ministries working in these areas.

Typical engagements include:

• Architecture session (90 minutes) – $500
• Implementation sprint – starting at $2,500
• Ministry / Foundation advisory engagement – $2,500

§Early Adopters

I’m also looking for early adopters interested in running Continuum, a local-first publishing and identity system built on Nostr.

There is no cost for early adopters, and I’m happy to personally help with installation and setup.

Even if you’re just curious and want to see how it works, feel free to reach out.

Feedback from early adopters directly influences the direction of the project.

Contact: andrewgstanton@gmail.com
or DM on Nostr:

@9wvc…guvd

You can also support this work as a Continuum Patron ($250).