Portable player identity
Request a game-specific pseudonym, device proof, competition persona, parental approval, or age claim rather than a universal social profile.
Software · games · digital products
Build the product—not an account empire.
Give applications portable identity, scoped access, direct sessions, signed distribution, entitlements, and replaceable operations without making one vendor the permanent owner of every player, customer, device, and deployment.
Game development
Small studios get infrastructure without surrendering the player relationship.
A studio can compose identity, private tests, multiplayer discovery, community servers, distribution, and proof of purchase while asking each player for only the claim that a particular workflow needs.
Games as entitlements
Represent edition, supported devices, offline use, family use, expansions, multiplayer, beta access, and transfer rules as signed rights.
Paid and private builds
Grant a branch, preview, founder edition, mod kit, server, or time-limited demonstration to an exact cohort and device allowance.
Community-operated servers
Let a persistent server identity move between studio, player, tournament, regional, or managed infrastructure without becoming a new server.
One session, no social graph
An expiring capability can open one lobby, match, spectator seat, private server, or remote stream without permanent friendship state.
Use the GPU you own
Discover a personal gaming machine, authorize the session, and use a direct route whenever possible. Any future paid relay remains explicit.
Applications and SaaS
The service remains stable while every machine beneath it can change.
Software may run on a laptop, a home server, a VPS, a regional provider, or a cluster. Signed service identity and short endpoint evidence separate what the service is from where it happens to run now.
Signs the service, access modes, key commitments, and policy.
Presents a short lease for the current approved endpoint.
Names the user, device, action, audience, right, and expiry.
Verifies locally, then serves its own bytes and owns its own state.
SaaS without captivity
A managed application can still provide excellent operations, collaboration, and support. The difference is that identity, compatible data, rights, and service continuity have an intentional exit instead of existing only as rows in one provider’s tenancy database.
Distribution and licensing
Ship signed software. Grant a right. Keep the storefront replaceable.
Distribution, payment, update delivery, device limits, and feature access are separate responsibilities. A developer can select different providers for each or run them directly.
Signed channels
Publish stable, nightly, preview, private, or customer-specific artifacts through independently verifiable release channels.
Scoped licenses
Bind access to one feature, build, organization, cohort, device count, usage allowance, support period, or expiration.
Community software
Mod creators can distribute updates, source assets, private builds, compatibility claims, and commercial-use permission.
Evidence that travels
Where product policy permits, portable evidence can support bounded offline use without contacting the store for every launch.
Provider-independent delivery
Clients verify publisher signatures whether a build came from the developer, a cache, a mirror, or a selected managed provider.
No compulsory platform tax
A payment or catalog provider is paid for the service it performs; it does not automatically own all future access or revenue.
Real-time and developer infrastructure
Events become a capability—not a permanent third party in every conversation.
Applications can authorize notification channels, direct sessions, delivery providers, and bounded offline retention independently from the rest of their data model.
Scope a channel to a user, device, team, project, service, session, category, priority, quiet hours, and retention rule.
Keep a forge private while granting contributor identity, temporary project access, build distribution, notifications, and paid releases.
Attach an editor, build worker, test server, database, or review app without placing the entire environment on a flat public network.
Combine an existing application with user-selected compute, storage, identity, certificates, access, backup, monitoring, and support.
CURRENT EVIDENCEDaemonet has implemented signed private services, profile DNS, two-sided network policy, device-bound access passes, and direct WireGuard paths.REMAINS GATEDProduction SDK stability, public provider networks, automated application provisioning, and broad software catalog claims require release and field evidence.
Existing software, reconnected
Thunderbird is the first reference lab.
Use an open mail client with a server you operate, private mailbox access over Daemonet, and a deliberately separate public SMTP edge.