Eggstr
Eggstr gives you a hosted shelf for Nostr and Bitcoin services. The NWC part comes from the wallet service you deploy or from Eggstr's own subscription payment flow, so the practical review is about domains, storage, relays, media, backups, upload rules and wallet permissions.
What Eggstr really is
Eggstr is a hosting surface for Nostr and Bitcoin applications. Its homepage says the offer plainly: deploy Nostr and Bitcoin apps with your domain, get access to all apps through a monthly subscription, and use a simple hosted flow instead of wiring each service yourself.
That wording is important because Eggstr can otherwise be misread as a wallet. It is not the wallet protocol, not a Lightning node implementation, not a Nostr relay protocol by itself and not the NIP-05 specification. It is the platform where several of those things can be launched and kept reachable.
For a reader coming from Nostr Wallet Connect, Eggstr belongs in the cloud-node shelf because one of the deployable apps is Alby Hub. Alby Hub can expose a wallet or Lightning node to NWC-compatible apps. Eggstr hosts that app; Alby Hub handles the wallet-service layer; Nostr relays carry the encrypted NWC messages; the Lightning backend pays or receives.
That makes Eggstr useful in a specific way. It lowers the setup friction for people who want an always-on Nostr or Bitcoin service with a domain. It does not remove the usual responsibilities around admin credentials, app backups, wallet permissions, relays, media uploads or identity records.
Why the cloud-node category fits
The getAlby awesome-nwc map lists Eggstr under cloud hosting of NWC nodes, describing it as easy deployment of Nostr and Bitcoin apps with an own domain. That category is a practical shortcut, not a statement that every Eggstr app is a wallet.
The strongest NWC fit is Alby Hub. Alby Hub's README says it lets you control your Lightning node or wallet from any application that supports NWC, and that it can run as a desktop app or as an HTTP web app. Eggstr gives that HTTP-style app a hosted home.
Eggstr also accepts Nostr Wallet Connect for its own Lightning subscription payments. That matters because a user can pay for the hosting service with the same app-to-wallet pattern they may be deploying. Still, paying Eggstr by NWC is different from using Eggstr as your wallet service.
The clean mental model is simple: Eggstr hosts the app. Alby Hub, LNbits, strfry, Haven, Blossom or the NIP-05 service define what the hosted app does. If an app connection can spend through NWC, the spending authority sits with the wallet service and its connection settings, not with the label on the Eggstr card.
The current app bundle
The Eggstr homepage checked for this article listed six main app tiles: LNbits, Alby Hub, strfry, Haven, Nostr Address and Blossom Server. The site presents the bundle as all apps from $20 per month and shows Basic, Standard and Premium plans with 20 GB, 50 GB and 100 GB of storage.
Those six apps cover different responsibilities. LNbits is a Lightning wallet and accounts toolkit. Alby Hub is a personal wallet-service and app-connection layer. strfry is a Nostr relay. Haven is a personal relay stack with private, chat, inbox and outbox behavior plus a Blossom media server. Nostr Address maps names on a domain to public keys through NIP-05. Blossom Server stores blobs for Nostr media flows.
That mix explains why Eggstr is not easy to place in a single old-fashioned app category. It is part self-hosting panel, part Nostr service shelf, part Lightning-adjacent hosting and part custom-domain product. The app you deploy determines whether the result feels like a wallet, a relay, a media server or an identity endpoint.
Before you buy a plan, write down which app you actually need. A person who only wants a verified NIP-05 address has a different risk profile from someone running an Alby Hub with real funds. A person running a Blossom server has different storage and moderation questions from someone running strfry for a small relay.
Alby Hub is the NWC center
Alby Hub is the Eggstr app that most directly explains the NWC category. The Eggstr app card says Alby Hub lets you control your Lightning node or wallet from any other application that supports NWC. The upstream Alby Hub README says the same thing and adds that Hub can connect apps such as Damus and Amethyst to your node.
That makes a hosted Alby Hub attractive if you want wallet connections but do not want to run a home server. NWC works best when the wallet service is reachable when apps ask for payments or invoices. A hosted Alby Hub can provide that always-on surface, assuming you are comfortable with the hosting dependency.
The important boundary is custody and access. Alby Hub may be self-custodial depending on backend and setup, but a hosted deployment still has admin credentials, application data, connection strings and recovery material. If you deploy Hub on Eggstr, your practical safety depends on the Hub configuration, the backend, the domain, the login path and your backup discipline.
Treat each NWC connection as a spending permission. Name connections clearly, set conservative budgets where the wallet supports it, use tiny test amounts first and revoke old app connections. A clean cloud deployment can still become dangerous if every social client receives a broad, permanent payment permission.
LNbits is a different tool
LNbits appears next to Alby Hub on Eggstr, but it should not be described as the same kind of app. LNbits describes itself as a lightweight Python server that sits on top of a Lightning funding source. It gives isolated wallets, an API and an extension system.
That makes LNbits excellent for workshops, prototypes, small services and app builders who need account-like wallets or extension-driven Lightning features. It can also become a serious responsibility if you expose it to other people or connect it to meaningful funds.
For Eggstr, the question is what role LNbits plays in your stack. If you are using it as a personal tool, the main checks are admin access, wallet keys, funding source, API exposure and backups. If you are using it for a community, shop, workshop or public app, user boundaries and extension risk become more important.
Do not assume LNbits on Eggstr inherits Alby Hub's NWC behavior. LNbits can participate in NWC-related ecosystems through plugins and integrations, but the exact installed extension, funding source and API exposure determine what is available. Verify the app itself after deployment rather than relying on a category name.
strfry is the relay option
Eggstr's strfry card is for people who want their own Nostr relay server. Upstream, strfry calls itself a relay for the Nostr protocol and highlights local LMDB storage, support for many applicable NIPs, durable writes, streaming, JSONL import/export, negentropy-based reconciliation and Prometheus metrics.
A relay is not a wallet. It is the database and transport surface where Nostr events are accepted, stored, rejected, served and sometimes synced. If you run strfry on Eggstr, you are becoming a small relay operator, even if the hosting flow makes that feel like clicking a button.
The operational questions are different from Alby Hub. Which event kinds will the relay accept? Is it public, private or semi-private? Does it require NIP-42 authentication? Does it publish a NIP-11 relay information document? How much storage do events consume? How will you compact, export, import or migrate the relay database?
This is where Eggstr's storage tiers matter. A relay can grow quietly. A tiny private relay for your own notes is one thing; a public relay that accepts large volumes of events is another. Before opening a relay broadly, test write rules, read rules, rate limits, moderation, storage growth and export paths.
Haven changes the relay story
Haven is more opinionated than a plain relay. The Haven README describes it as High Availability Vault for Events on Nostr and says it is a personal relay for storing and backing up sensitive notes such as ecash, private chats and drafts. It is considered feature complete in the current upstream note and is expected to receive bug fixes in Barry Deen's repository.
Haven bundles four relay roles plus Blossom media behavior. Its README describes a private relay for drafts and other private notes, a chat relay for DMs and group chats, an inbox relay for notes where the owner or whitelisted users are tagged, and an outbox relay for public notes. It also includes a Blossom media server.
That is why the Eggstr card says Haven is four relays in one plus a Blossom Media Server. It is not just another relay binary. It is closer to a personal Nostr home with whitelisting, web-of-trust assumptions, backup/restore, note import and media upload rules.
If you deploy Haven on Eggstr, spend extra time on owner keys, whitelists, auth, backups and media rules. A personal relay that holds private drafts, ecash-related events or chat data deserves a more careful setup than a disposable test relay.
Nostr Address is NIP-05
Eggstr also offers Nostr Address. The site describes it as NIP-05 linking human-readable addresses on a domain to Nostr public keys. That is exactly the lane NIP-05 occupies: mapping Nostr keys to DNS-based internet identifiers.
NIP-05 is useful because people can recognize a name like `alice@example.com` more easily than a long public key. The spec says clients fetch `/.well-known/nostr.json?name=...` on the domain and compare the returned public key with the profile's public key.
The spec also warns against overstating what the identifier proves. NIP-05 is identification, not universal verification. It is stronger when the person or project is meaningfully connected to the domain, but clients still need to follow public keys, not replace follow lists whenever a domain record changes.
For Eggstr users, the practical checklist is DNS, HTTPS, the exact JSON response, CORS headers, no redirects on the well-known endpoint and a plan for migration. If your NIP-05 address becomes part of your public identity, you need to know what happens when the Eggstr plan ends or the domain changes.
Blossom is media storage
Blossom Server is Eggstr's media-storage app. The Blossom repository describes Blossom as a specification for HTTP endpoints that allow users to store blobs of data on publicly accessible servers. It uses Nostr public and private keys for user identities, and blobs are addressed by SHA-256 hash.
That means a Blossom server is not just an image folder. It is a Nostr-adjacent media service with upload, retrieval, deletion, mirroring, reports and authorization documents. Eggstr's page frames it for ordinary users as a personal media server for images and files used in Nostr posts.
The user-facing promise is simple: store media under a server you control. The operator-facing reality is broader: file types, size limits, upload authorization, public retrieval, abuse reports, retention, payment requirements if enabled, storage quotas and deletion behavior all matter.
If you deploy Blossom on Eggstr, start with a whitelist. Confirm who can upload, how links are formed, whether files are public, how you remove content and how quickly storage grows. A media server is easy to start and surprisingly easy to fill.
Paying Eggstr with NWC
Eggstr's pricing section says it accepts Nostr Wallet Connect for seamless Lightning payments. That is a notable product choice because it puts the service inside the same wallet-connection world that many of its users are exploring.
NWC itself is an open protocol that connects Lightning wallets to apps. The NIP-47 spec describes a client, a user and a wallet service. The wallet service typically runs on an always-on computer, perhaps in the cloud or on a Raspberry Pi, and communicates with clients through encrypted Nostr events over relays.
When you pay Eggstr with NWC, Eggstr is the app requesting payment from your wallet service. When you deploy Alby Hub on Eggstr, Alby Hub may become the wallet service for other apps. Those are two different directions of authority.
Keep those flows separate in your notes. A subscription payment should have one limited payment context. An Alby Hub app connection for a social client should have its own budget and revocation path. A hosted service becomes easier to reason about when each NWC relationship is named and tested.
Domains and storage are part of the product
Eggstr's value is not only the app list. The site repeatedly emphasizes custom domains: use an `xxx.eggstr.com` address or your own domain. For NIP-05, relays and Blossom, that domain layer is not cosmetic. It is the public address where clients and people will look.
The storage tiers matter for the same reason. The Basic plan shows 20 GB, Standard shows 50 GB and Premium shows 100 GB. That may be plenty for a NIP-05 service or a small Alby Hub, but it can disappear faster with media uploads, relay data or Haven backups.
Ask storage questions before you need an emergency answer. Does the plan include all app data in the quota? How are backups counted? What happens when the quota is exceeded? Can you export data before cancellation? How large is a typical Blossom library or relay database after a month of real use?
A custom domain makes migration both easier and more serious. Easier, because you can point the domain elsewhere later. More serious, because users and clients may learn to trust that address. Document DNS, records, app URLs and renewal dates as part of the deployment, not as an afterthought.
Operator signals and support
Eggstr's footer links to a Nostr support profile and to BTCMVP. BTCMVP describes itself as a Bitcoin development solutions company offering Bitcoin app work, Lightning node setup, payment servers, ecommerce integration, node management and security services.
That context is useful, but it should not be stretched into guarantees. A footer link and a support profile help you find a human path, but they do not replace service terms, export tools, uptime history, incident handling or restore documentation.
Support via Nostr fits the product's culture. It is quick, native and less account-heavy than many ticket systems. For infrastructure with funds or identity attached, you still want boring records: plan ID, app names, domains, invoices, admin email if any, Nostr support profile, backup notes and restore expectations.
If Eggstr becomes important to your daily workflow, run a support drill while stakes are low. Ask a non-urgent question, confirm the response path and note what information you should provide without exposing secrets. Infrastructure support is easiest when you have already learned the route before something breaks.
What Eggstr does not do
Eggstr does not make every hosted app production-safe by default. It can make deployment easier, but upstream app maturity still matters. Alby Hub, LNbits, strfry, Haven and Blossom each have their own release cadence, security model, configuration choices and failure modes.
Eggstr does not turn NIP-05 into proof of identity beyond what the spec says. It can host the well-known JSON endpoint, but the relationship between a person, a public key and a domain still depends on domain control and client behavior.
Eggstr does not make a relay maintenance-free. strfry and Haven can be powerful, but relay storage, event policy, auth, imports, exports and abuse handling remain part of operating a relay. A small private relay can be simple; a public relay can become work.
Eggstr also does not remove wallet risk. If you deploy Alby Hub or LNbits and connect money, you are responsible for understanding how funds are controlled, how secrets are stored, how backups work and how permissions are revoked. Hosting is a convenience layer, not a substitute for wallet review.
Security checks before real use
Start with access. Confirm how you log in to Eggstr, how the app admin login works, what recovery path exists and whether you can separate the Eggstr account from app-level administrator credentials. A hosted Alby Hub, LNbits instance, relay or media server should not rely on one forgotten browser session.
Then check the public surface. Open the app from a clean browser. Confirm HTTPS. Confirm whether admin pages are protected. If a relay should be private, attempt to write from an untrusted client and confirm it fails. If Blossom should restrict uploads, test an unauthorized upload attempt.
Next check data movement. For NIP-05, fetch the `/.well-known/nostr.json` URL and validate the exact public key. For strfry or Haven, export a small event set if possible. For Blossom, upload and delete a harmless test file. For Alby Hub or LNbits, back up before funding.
Finally check NWC with tiny limits. Pay a tiny invoice, make a tiny invoice, create a named app connection, revoke it and confirm the old app cannot continue spending. Do this before connecting multiple Nostr clients or storing meaningful funds.
Good uses for Eggstr
Eggstr is a good fit when you want a public Nostr or Bitcoin service quickly and do not want to manage a VPS by hand. A creator can deploy NIP-05 and Blossom. A developer can run LNbits for a small test. A Nostr user can try a personal relay. A NWC user can host Alby Hub and learn the app-connection flow.
It also fits people who care about domains. Having your own address for a relay, media server or identity endpoint is often cleaner than relying on a random local machine or a changing tunnel. Eggstr makes that a front-door feature instead of an advanced step.
The product is less ideal if you need full hardware control, custom networking, strict institutional compliance or very large public infrastructure. A hosted bundle is fast, but a serious public relay, production payment service or large media host needs monitoring, legal thinking, abuse handling and a migration plan.
The best first project is small and reversible. Deploy one app, test it, document it and delete or migrate it if it does not fit. Eggstr's strength is speed; your job is to prevent speed from turning into unmanaged dependency.
What to compare it with
Compare Eggstr with Alby Cloud if your main goal is Alby Hub with minimal setup. Alby Cloud is more directly centered on Hub, while Eggstr offers a broader Nostr-and-Bitcoin app shelf with relays, NIP-05 and Blossom alongside wallet tools.
Compare it with Start9, Umbrel, RaspiBlitz, CasaOS and Unraid if you want home-server control. Those systems shift responsibility back to your hardware, network, storage and update rhythm. Eggstr shifts more of the deployment surface to a hosted provider.
Compare it with a plain VPS if you are comfortable with Linux, Docker, reverse proxies, backups and DNS. A VPS can be more flexible and cheaper at scale, but Eggstr should be faster for users who want the app running before they want to become server administrators.
The right choice is not ideological. Choose the path whose failure mode you can handle. If losing a hosted account would be painful, plan export and migration. If maintaining a home server would be painful, hosted infrastructure may be the calmer choice.
The bottom line
Eggstr is a small but useful piece of the Nostr infrastructure story. It gives you a hosted place to run Alby Hub, LNbits, strfry, Haven, Nostr Address and Blossom without turning every user into a full-time operator.
Describe it honestly and it becomes easier to use safely. Eggstr hosts. Alby Hub handles NWC wallet-service behavior. LNbits handles Lightning accounts and APIs. strfry and Haven handle relay behavior. NIP-05 handles name-to-key lookup. Blossom handles media blobs.
The risks follow those layers. Wallet permissions belong to the wallet app, relay policy belongs to the relay, media abuse belongs to the media server, and domain trust belongs to DNS and NIP-05 records. Eggstr can package the deployment, but it cannot make all those choices for you.
Use it as an accelerator, not as magic. Start small, pay with a limited NWC connection, deploy one app, test the domain, test backups, test revocation, document recovery and only then decide whether Eggstr should carry a larger part of your Nostr or Bitcoin life.
Sources worth opening
Open Eggstr first, then compare the upstream pages for Alby Hub, LNbits, strfry, Haven, Blossom, NIP-05 and NIP-47. Those sources keep the layers separate: Eggstr hosts; the deployed app defines the wallet, relay, identity or media behavior.
- Eggstr home page
- getAlby awesome-nwc list
- Nostr Wallet Connect site
- Nostr Wallet Connect docs
- NIP-47 Nostr Wallet Connect
- NIP-47 raw specification
- Alby Hub official site
- Alby Hub GitHub repository
- Alby Hub raw README
- Alby Hub releases
- Alby app connections via NWC
- LNbits official site
- LNbits GitHub repository
- LNbits raw README
- LNbits releases
- strfry GitHub repository
- strfry raw README
- strfry releases
- Haven GitHub repository
- Haven raw README
- Haven releases
- Blossom GitHub repository
- Blossom raw README
- Blossom BUD-01 server requirements and retrieval
- Blossom BUD-02 upload and management
- Blossom BUD-11 Nostr authorization
- NIP-05 mapping Nostr keys to DNS identifiers
- NIP-05 raw specification
- NIP-11 relay information document
- NIP-42 relay authentication
- NIP-98 HTTP auth
- BTCMVP home page
- Eggstr Nostr support profile
- Moonstr Eggstr wall embed
