CraysSatlantis
Satlantis is one of the more revealing Nostr products because it has stopped trying to win the feed war. Its center is events: people gathering, organizers selling tickets, communities building calendars, curators sharing places and the social graph becoming useful because it points back to the physical world.
The feed was not the point
Satlantis makes more sense once you know what it decided not to be. Early public writing around the product described a travel-centric social network, something between TripAdvisor, Meetup and Instagram, built for nomads and Bitcoin people. That idea is still visible in the app's DNA: places, profiles, maps, collections, local recommendations, social discovery. But the more recent public story is sharper. Satlantis is now an events-first platform. The product is for hosts, organizers, communities and attendees who need the internet to do something that ends in a room, a conference, a dinner, a retreat, a workshop or a recurring meetup.
That pivot matters because Nostr already has strong feed clients. If Satlantis tried to beat Primal, Damus, Amethyst or noStrudel at the timeline game, it would be just another app asking users to post somewhere else. The Satlantis team has said this problem out loud in its own blog: feeds are difficult, and another social app is not enough. The better question is whether Nostr's identity and social graph can make a practical tool more useful. Who is going to this event? Which place did someone I trust bookmark? Which city has people, venues and gatherings that fit my actual life? That is a more interesting battlefield.
So do not read Satlantis as a "Nostr client" in the narrow sense. Read it as an event operating system with Nostr under the floorboards. The visible product is event creation, discovery, ticketing, calendars, guest communication and collections. The Nostr part is identity, signing, social graph and portability. The Bitcoin part is global money for tickets and host payouts. The useful question is not "is this decentralized?" The useful question is: which parts of the event life cycle become easier, more global or less trapped because Satlantis uses Bitcoin and Nostr?
What you can actually do
The official FAQ describes Satlantis as a Bitcoin-native social events platform. It lets people create, manage, discover and monetize events while building community around them. The App Store page puts the same thing in a more product-shaped list: create or import an event, get paid with Bitcoin-native ticketing, grow and own an audience, organize calendars, go beyond events by adding venues and collections of recommended places. The homepage shows the same priorities: create or import events, browse featured events, build collections, power communities and discover who is in town.
For the organizer, that means Satlantis is not only a listing page. You can create an event, define tickets, work with capacity and visibility, collect payment, communicate with attendees and build a profile that keeps future gatherings connected to the same audience. The February 2026 product update says event organizers gained improved announcement tools with filters for approval status, attendance status, people who have not bought tickets yet, declined invitees and even custom CSV uploads. That is not Nostr hobby language. That is event CRM language.
For attendees, the experience is closer to discovery. Satlantis wants to know your interests and then surface events, places and collections through a social lens. The app pitch is that a city is not one generic map. It changes depending on whether you are looking through the eyes of a foodie, a surfer, a Bitcoiner, a remote worker, a health person, a nightlife person or a founder looking for the right room. The old internet gives you rankings. Satlantis tries to give you context.
Events are the business model
The events focus is also where Satlantis becomes more than a catalog of meetups. The FAQ says organizers can monetize through tickets, memberships or both. It says each event comes with built-in payments and a dedicated Bitcoin and stablecoin wallet, with Bitcoin and stablecoin withdrawals to the organizer's own wallet and fiat payouts through Stripe. The same FAQ says Satlantis supports credit cards, Apple Pay and Google Pay through Stripe alongside Bitcoin and stablecoins.
The February 2026 product update gives the clearest payment detail. It says every Satlantis account has a built-in Bitcoin Lightning wallet, used to pay, send and receive. It also says hosts can use it to buy event tickets with one click, withdraw Bitcoin earnings from hosted events and eventually send sats to attendees. The post is careful about custody: the wallet is custodial and users are encouraged to keep small amounts there and withdraw when the tradeoff no longer feels comfortable. That sentence is valuable because it keeps the Bitcoin story honest.
Fiat is there too. The same update says Stripe support was added so non-Bitcoin users can pay in familiar ways. The March 2026 update adds multi-currency support at the event level, so an organizer can charge one event in USD and another in EUR or CAD, while Stripe handles fiat conversion. Satlantis is not pretending that every attendee already lives on Lightning. It is trying to make Bitcoin part of the event workflow without turning every event into a Bitcoin tutorial.
Who is behind it
The app-store developer is Laier Two Labs. Apple lists the seller as Laier Two Labs, Inc, and Google Play lists Laier Two Labs as the developer. The official Satlantis about page names Aleksandar Svetski as CEO, Robert Allen as CTO and Niel Liesmons on design. It gives Svetski the shorthand of a multi-exit founder with consumer app experience, Allen as a full-stack developer and producer of the Bitcoin and Friends animated series, and Liesmons as a UI/UX designer for Nostr and Bitcoin apps. Satlantis blog updates are frequently signed by Jordi Llonch Esteve as Head of Growth.
That team context helps explain the product's tone. Satlantis is not a neutral calendar utility. It has a worldview. It speaks to Bitcoiners, nomads, creators, sovereign individuals, event hosts and communities that want to own their audience. It borrows from travel, social networking, local discovery, Bitcoin meetups and creator tools. Some readers will love that. Some will find it too culturally specific. Either way, it is not hiding the crowd it wants first.
The official site also currently carries a crowdfund banner through Timestamp. That is a business signal, not a product feature, and this article is not investment advice. It does tell you that Satlantis is not only a side project floating in the Nostr app shelf. It is being built as a company, with funding, app-store distribution, paid plans, support channels and the ordinary obligations that come with handling payments, user content and attendee data.
The Nostr part is login, signing and social context
Satlantis uses Nostr most visibly at login. The site's sign-in modal offers email, Apple, Google, Nostr and Whop. The about page and FAQ show a Nostr signing prompt that asks the user to approve event signing for Satlantis.io, with a note that browser extensions may open a separate signing request. That points to the familiar Nostr web pattern: an app prepares an event and asks a signer to approve it instead of simply treating the user as an email account in a database.
The March 2026 product update adds another important piece: Primal signer integration. Satlantis explains it in plain language: users should not have to trust Satlantis with a raw private key, and Primal users can log in and sign Nostr events on Satlantis without giving Satlantis the key. On the web, Nostr browser extensions usually map to NIP-07. Remote or account-based signing belongs near the NIP-46 conversation, although the exact Primal signer flow should be verified in the app rather than guessed from the blog. The design principle is clear either way: the better version of Satlantis is one where Satlantis can ask for signatures but does not become the permanent owner of the user's Nostr key.
For readers, the practical test is simple. Sign in with Nostr, create or interact with one low-stakes item, and watch what gets signed. Does the signer show you enough context? Can you use the same Nostr identity elsewhere? Does your Satlantis profile connect to your broader social graph, or does it quietly become a separate account with Nostr branding on top? A good Nostr product should make the answer visible.
Calendar standards are the interoperability test
Events are one of the best use cases for Nostr because they naturally need identity, signatures, location, RSVPs, updates and discovery across communities. NIP-52 is the Nostr calendar-events specification. It defines date-based calendar events, time-based calendar events, calendars and RSVP events, with fields for title, summary, image, location, geohash, participants, tags and references. In NIP-52, time-based calendar events use kind 31923, calendars use kind 31924 and RSVPs use kind 31925.
This is the standard Satlantis should be compared against. The public Satlantis pages clearly show event creation, calendars, Nostr sign-in and signing prompts. They do not, from the public pages alone, prove exactly which event kinds Satlantis publishes for every feature. So the honest article does not claim more than it can see. The right interoperability question is: when a Satlantis event is created or RSVP'd to, can another NIP-52-aware client understand it? Can a calendar event leave Satlantis and remain useful on a relay? Can the organizer's audience be reached through npubs and Nostr events instead of only through Satlantis dashboards and emails?
If Satlantis answers that question well, it becomes much more than a polished events app. It becomes a bridge between the ordinary event world and the open social web. If it answers it weakly, it is still a useful app, but with more of the important behavior inside its own product boundary. That distinction is exactly why Nostr readers should care.
Places and collections are the sleeper feature
The collections feature is easy to underestimate. Satlantis describes collections as lists of places that can be shared, saved, made public or private, used standalone or linked to an event. The homepage compares them to playlists for places. The Beyond the Feed article explains the deeper idea: places and collections become more useful when the social graph tells you who recommended, saved or attended what.
This is where Satlantis moves away from the usual event-platform comparison. Eventbrite is mostly ticketing. Meetup is mostly community and events. Luma is elegant event hosting. Google Maps is a giant place database. Instagram is where people accidentally discover where to go. Satlantis wants to weave those behaviors together: an event can recommend nearby places, a conference can have side-event agendas, a host can build a local guide, and attendees can carry those recommendations into the rest of their trip.
For Crays, this part is especially relevant. Events are not only calendar entries. They are restaurants, hotel lobbies, rooftops, coworking spaces, beaches, workshops, afterparties, health routines, city districts and the people who know where the good rooms are. A Nostr identity plus a curated map could make a venue relationship more durable than a one-time ticket sale. That is the quiet promise inside Satlantis.
Mobile status and platform reality
Satlantis is not only a web page. Apple lists Satlantis: Social Events as a free iPhone app from Laier Two Labs, in Social Networking, with iOS 15.1 or later required. The App Store page describes event creation, Bitcoin-native ticketing, calendars, audience growth and collections. It also shows an update history through version 0.48.44 on February 19, 2026. Google Play lists the Android package as `com.satlantis.satlantis`, developer Laier Two Labs, 1K+ downloads, parental guidance content rating and an update date of February 19, 2026.
Those store pages are useful because they show Satlantis is being shipped and updated through normal consumer distribution channels. They also show the privacy surface. Apple says the app may use usage data to track users across apps and websites, and may link location, contact info, user content, identifiers and usage data to the user's identity. Google Play says the app may share personal information with third parties, may collect personal information, photos and videos, and device or other IDs, encrypts data in transit and lets users request deletion.
That does not make Satlantis uniquely bad. It makes Satlantis a real app. Real events require names, contact, payments, location, media, tickets and organizer tools. The privacy question is not whether data exists. It is whether the product gives users and hosts a clear deal: what is public, what is private, what is on Nostr, what is in Satlantis, what is in Stripe, what is in the custodial wallet and what can be exported or deleted.
Where it is strongest
Satlantis is strongest for organizers who already feel the limits of generic platforms. A Bitcoin meetup in Prague. A freedom conference with side events. A wellness retreat with curated local places. A recurring workshop that wants paid membership and not just one-off tickets. A nomad community that needs events, city context and identity in the same product. In those cases, the app's mix of calendars, ticketing, social discovery and Bitcoin payments becomes coherent.
It is also strong as an onboarding bridge. A person may not care about Nostr on day one. They care that they got a ticket, found a place, joined a calendar or met the right people. If the product quietly gives them a Nostr identity, a social graph and a way to receive sats, then the protocol stops being an abstract lecture. It becomes something that happened because the event was useful.
That is the healthiest Nostr path. Not "come use my protocol." More like: come to the thing you already wanted to do, and discover that the account, the payment and the social relationship are less trapped than before.
Where you should be careful
The caution starts with key custody and signing. Satlantis deserves credit for adding Primal signer support and for saying users should not trust the app with an nSec. Still, every Nostr sign-in flow should be watched carefully. Use a signer. Read the prompt. Start with low-stakes actions. If you are an organizer with real revenue and attendee data, do not learn the permission model five minutes before ticket sales open.
The second caution is payment custody. The built-in Lightning wallet is custodial by Satlantis' own description. That can be the right tradeoff for onboarding and tiny payments, but it is still a tradeoff. Hosts should understand how withdrawals work, what fees apply, which payment rails are active for their event, and how fiat, Bitcoin and future stablecoin flows appear in their accounting.
The third caution is interoperability. Satlantis may be the best tool for running the event, but a Nostr-native claim should be tested outside Satlantis. Can the public event be found elsewhere? Can your npub audience survive if you leave? Can calendar or RSVP data be understood by another client? Can your community contact list be exported or reached without the Satlantis interface? These are not hostile questions. They are the questions that make the product better.
The human read
The reason Satlantis is interesting is not that it adds Bitcoin and Nostr labels to a normal app. The reason is that events are one of the rare places where the open stack has an obvious human job. People want to meet. Hosts want to sell tickets without being trapped by region, currency or platform gatekeepers. Communities want recurring relationships, not a pile of one-off registration forms. Travelers want a city map that knows what kind of person they are becoming.
Satlantis is trying to make that feel like one product. It may be messy because the problem is messy. Payments, calendars, signers, profiles, places, media, guest lists, privacy and real venues do not fit neatly into a tiny app-store description. But the direction is right: less infinite feed, more real life. For Nostr, that is valuable. The protocol does not need every app to be a timeline. It needs apps that make the public-key social web useful in situations where people can feel the difference.
If you are a host, test Satlantis by creating one small real event and following the whole path: sign-in, event creation, tickets, payment, attendee communication, calendar visibility and post-event audience ownership. If you are a reader, watch Satlantis because it is one of the apps asking the right question: how do we use open identity and open money to make the offline world easier to organize?
Sources worth opening
This article separates the official product claims from the protocol comparison. Start with the official pages, then check the app stores and relevant NIPs.
- Satlantis official site
- Satlantis FAQ
- Satlantis about and team page
- Satlantis profile on Satlantis
- Satlantis on the App Store
- Satlantis on Google Play
- Satlantis: Beyond the Feed
- Satlantis: Bitcoin Wallet and Stripe update
- Satlantis: Primal signer and multi-currency update
- Satlantis: building the first Nomad Super App
- TFTC interview notes with Aleks Svetski
- Satlantis LinkedIn company page
- Aleksandar Svetski Nostr profile
- Satlantis Nostr profile via Damus
- NIP-52 Calendar Events
- NIP-07 NIP-07 Signers
- NIP-46 Nostr Connect
- NIP-57 Lightning Zaps
- Satlantis privacy policy
- Satlantis terms of use
- Satlantis on NostrApps
- NIP-25 reactions
- NIP-27 text note references
- Nostr protocol NIPs repository
- NIP-01 basic protocol flow
