01
Owner-controlled identity
Let people establish a durable NightFall identity without requiring a phone number as the permanent identifier.
05
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
The project unifies encrypted messaging, protected calling, device enrollment, synchronization, backup, and recovery within one owner-controlled communications system.
Android and iPhone/iPad are mandatory product targets. Native applications are intended to share a security-critical Rust core through platform-specific Kotlin and Swift bindings while preserving native mobile behavior.
Pulse is a separate NightFall project. It can integrate with NightFall Continuum through service-scoped Presences when that protection is available, but it must identify the active transport honestly and never silently claim protection it cannot provide.
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.
Defined
Product boundary
The owner-controlled identity, communications, recovery, and transport requirements have been established.
2 platforms
Mandatory clients
Android and iOS/iPadOS are both required deliverables.
Shared core
Implementation direction
Security-critical logic is designed around a Rust core exposed through native Kotlin and Swift bindings.
Phase 0
Current scope
The first implementation boundary covers enrollment, synthetic encrypted messaging, backup and restore, and an honest Continuum transport interface.
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.
- Encryption, metadata protection, recovery, device revocation, and cross-platform behavior require implementation and reproducible validation before production claims are made.
- 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