Project status & roadmap

Windows-first development release

Secretinio is being built as a password manager for organizations and personal vaults, with installed clients and independently hosted servers. The current delivery is the Windows client and Secretinio Server (.NET 10). This is unaudited development software, and Windows builds are currently unsigned.

Implemented

Encrypted local vaults, typed records, custom password fields, nested groups, search, favorites, and encrypted backup/recovery.
One portable identity, multiple HTTPS servers, personal synchronization against your own Public-mode server, and conflict handling.
Windows Hello local unlock, server MFA, and separate organization TOTP/Windows Hello unlock.
Encrypted record/group sharing, recipient acceptance, permission checks, current-and-future sharing boundaries, and resumable rotation.
Server setup and administration, separate organization databases, organization roles, unique member names, and owner-verified identities.
Member filtering, access inspection, device/session controls, account containment, recovery custody, incidents, teams, permission templates, temporary access, reviews, approvals, and audit exports.

Mobile source status

Android and iPhone share the existing vault, sync, sharing and administration workflows. Mobile sources add phone navigation, native biometric key protection, clipboard privacy and encrypted backup export through system file pickers. Local identity unlock remains separate from each organization.

Organization biometrics use a TOTP-enrolled device key. The official Android client requires strong biometrics with hardware-backed keys; iOS uses Secure Enclave and the current biometric set. The server verifies the enrolled key, without remote hardware or biometric attestation. iOS can cover app previews and recording but cannot guarantee screenshot prevention.

Android toolchain preparation and SDK license acceptance are pending. iOS remains source-only in the Windows development environment and needs Mac/Xcode compilation. The manual iOS workflow produces an unsigned app; signing, emulator/physical-device testing and store releases remain pending.

Validated in the current implementation

The recorded server/Windows validation includes 118 server tests, 11 native security-library tests, 120 Flutter tests, clean static analysis, real HTTPS sharing/recovery/synchronization workflows, and a Windows release build. The sharing workflow includes interrupted rotation across more than one batch; recovery covers restart and a fresh recovery device.

These checks support the implemented workflows. They are not a security audit, hardware certification, or proof of production readiness.

Still to deliver

Android/iPhone platform compilation and emulator/physical-device validation, signing and store distribution. Native sources are implemented; no mobile download is claimed.
Android/iOS system autofill and credential-provider extensions.
A deployed default hosted personal service.
Publisher-signed installers, automatic updates, and a production release pipeline.
Independent security and protocol review, broader platform testing, and release hardening.
Stronger fresh-device assurance against a server withholding newer history, including ordered-journal coverage for ordinary revocations.
Offline organization unlock and reconciled individual-organization restore/import.

Release availability

Standalone Windows x64 and Linux x64 server packages are available from Server downloads, with SHA-256 checksums. They are framework-dependent and require the .NET 10 ASP.NET Core Runtime on the target machine. Packages are unsigned; Linux runtime validation remains pending. Read the self-hosting guide before installation.

See Downloads for available artifacts and platform status. A planned platform is not an available download.