01
Owner-controlled identity
Let people establish a durable NightFall identity without requiring a phone number as the permanent identifier.
06
NightFall Pulse
A unified mobile-first communications platform built around private identity, encrypted relationships, explicit recovery, and owner control.
The premise
Pulse is being designed so a person can communicate through an identity they control—without making a phone number, direct network address, or vendor account the permanent center of that relationship.
What it is
NightFall Pulse has a sealed official Android release candidate and a company-controlled messaging foundation. Production connectivity awaits the qualified Continuum transport and remaining hardware validation.
Android and iPhone/iPad remain product targets. The official Android release candidate is sealed but is not a public release.
Architecture
Public development priorities
02
Encrypted relationships
Protect messages, calls, synchronization, and relationship state with explicit cryptographic boundaries.
03
Native mobile clients
Deliver real Android and iOS/iPadOS applications rather than a desktop or web shell presented as a mobile product.
04
Shared security core
Keep security-critical behavior consistent through a shared Rust core with Kotlin and Swift platform bindings.
05
Explicit recovery
Make backup, restoration, enrollment, revocation, and recovery visible and controlled by the owner.
06
Continuum ready
Use service-scoped Continuum Presences when available, fail closed for protected calls, and never silently expose a direct IP.
Evidence
Current state
What has been demonstrated.
RC1
Official Android candidate sealed
The defined installation, restart, upgrade, signer, and stability checks passed.
Established
Messaging foundation
The company-controlled messaging foundation is prepared but not active in the application.
Blocked
Production transport
Genuine owner-production Continuum transport remains required.
No release
Current boundary
The sealed candidate is not a public product release.
Results describe preserved controlled tests and their defined scope. They do not convert unfinished long-term objectives into completed capabilities.
Boundaries
Protection must never be implied
- NightFall Pulse is not currently offered as a finished consumer communications product.
- A fixture or development transport must be identified clearly and must not be represented as Continuum protection.
- Protected calls must not disclose a direct IP address or silently fall back to an unprotected path.
- Application, packaging, privacy, evidence, signing, service integration, and release preparation remain separate validation boundaries.
- The sealed Android release candidate is not a public release.
- Continuum integration is optional and explicit; Pulse remains a separate project with its own product boundary.
Original work
What NightFall contributes.
Encrypted messengers, secure calling, device enrollment, recovery systems, and private-network transports each have substantial prior art. NightFall Technologies considers Pulse’s complete owner-controlled identity, relationship, recovery, native-client, and Continuum-integration architecture proprietary, with enabling details reserved for confidential review.
Our approach to originalityCompany-wide governance
Every NightFall system remains subject to the same responsibility and local-control boundary.
Product-specific capability does not override owner authority, neutral operation, transparent updates, accountable use, or the prohibition on hidden vendor control.
Read the governing framework