Nostrfi is the threenine product suite for Nostr infrastructure. It covers relay software, event storage, backend services, and the operator practices needed to run them dependably.

Can I use Nostrfi today?

The relay is in development and its source is public under the Nostrfi organisation. Storage, indexing, and backend services are defined scopes rather than released products, so check the repositories for current status.

Does threenine host relays for customers?

No. There is no hosted relay service, managed operations offering, or uptime SLA at this stage. Those promises will only be made when the underlying product and operating model exist.

Developers and client builders, relay operators, infrastructure operators, and organisations that need dependable backend foundations for Nostr applications.

How is Nostrfi different from Diogel?

Nostrfi owns Nostr infrastructure such as relays, storage, backend services, and operator workflows. Diogel owns Nostr signing, identity, and private-key protection. They are separate threenine product suites with separate problem spaces.

Where can I follow the work?

The Nostrfi GitHub organisation holds the public relay repository, and the threenine blog publishes the relay and infrastructure guides that explain the thinking behind it.

- Diogel
  Nostr signing and key-protection tools for safer identity workflows.
- Nostrfi
  Nostr relay, storage, and backend-service infrastructure for builders and operators.
- Nostr Product Development
  Focused engineering support for teams building Nostr-native products, tools, and protocol-aware user experiences.
- Bitcoin Product Development
  Specialist engineering for Bitcoin-native and Bitcoin-aligned products with stronger ownership, payments, and digital sovereignty models.
- About
  Learn more about Threenine, our direction, and why we build in this space.
- Blog
  Practical Bitcoin, Nostr, and product engineering guides.

Nostr infrastructure suite

Nostrfi

Nostrfi is the threenine suite for Nostr relay, storage, backend-service, and operator infrastructure.

Relay behaviour, retention, filtering, moderation, and observability are product decisions, not hidden server chores. Nostrfi keeps them in one place so they can be documented, tested, and operated deliberately.

Relay software
Event storage
Open source
Operator tooling

View the source nostrfi.io

Suite map

Nostrfi starts at the relay layer and expands outward only when a scope becomes concrete enough to operate.

01In development

Relay

Relay software and operations

A relay that accepts, stores, and forwards signed Nostr events, along with the policy, subscription, and operating decisions that come with running one.

For: Relay operators and teams that need a relay they understand.

View the source

02Suite direction

Storage and indexing

Event data layer

How events are stored, indexed, filtered, and retained over time, so query behaviour and retention policy stay predictable as volume grows.

For: Developers and operators with real data-retention decisions to make.

03Suite direction

Backend services

Protocol-aware services

The service patterns that Nostr clients need once protocol behaviour meets production operations, including deployment, monitoring, and reliability baselines.

For: Client builders and organisations shipping Nostr products.

What this suite owns

Nostrfi is the infrastructure half of the threenine portfolio. It exists so relay and backend decisions are explicit product concerns.

Relay software, relay policy, and the operating model around running a relay.
Event storage, retrieval, indexing, subscriptions, and filtering behaviour.
Retention and moderation choices, treated as decisions with documented trade-offs.
Deployment, observability, and reliability baselines for Nostr backends.
Protocol compatibility and implementation boundaries as first-class design inputs.
Operator documentation that makes infrastructure behaviour reproducible.

What it deliberately leaves alone

Nostr private-key custody and signing, which belong to the Diogel suite.
General-purpose hosting unrelated to Nostr infrastructure.
Client and social UX products that do not support relay or backend operation.
Hosted production services and managed operations, until the operating model exists.

Proof and maturity

Nostrfi is earlier than Diogel. This is what exists, what is being built, and what should not be assumed.

Proof today

Relay work in the open

A public relay repository under the Nostrfi organisation.
Published guides covering relays, relay choice, privacy, and security.
Protocol and operations research carried into the product work.

Suite direction

Storage, services, and operations

Storage and indexing behaviour defined as a product scope.
Protocol-aware backend services for client and application builders.
Deployment, monitoring, and reliability practice captured as runbooks.

Not yet

What to hold us to later

There is no hosted relay service and no managed operations offering.
No uptime, retention, or support SLA is being claimed on this page.
Storage, indexing, and backend services are scopes, not shipped products.

Where to start

Pick the route that matches the infrastructure decision in front of you.

Relay operator

Understand what you are running

Read the relay source and the operating guides before committing to a relay you cannot reason about. Retention, policy, and moderation choices are easier to make early.

View the relay source

Developer

Know how relays behave

Subscriptions, filters, and event storage decide what your client can actually do. Start with how relays work, then design around their real behaviour.

How relays work

Nostr user

Choose relays deliberately

Which relays you read from and write to shapes your reach, your privacy, and how durable your notes are. It is a choice worth making on purpose.

How to choose relays

Organisation

Plan for operations, not just deployment

Dependable Nostr infrastructure needs documented retention, monitoring, and reliability baselines. Follow the suite repositories as those scopes become concrete.

Follow the suite

Follow the infrastructure work

Nostrfi is being built in the open, starting with the relay. The source and the background guides are the honest picture of where it stands today.

View the source Read the relay guide