NUVQUERIO Open workspace

A focused security workspace for everyday secrets.

Nuvquerio brings local credential generation, code-based access and an encrypted personal vault into one clear workflow.

Open the password studio

Generate in your browser. Choose what to keep. Encrypt before saving.

One workflow, three deliberate steps

Choose a secret type, set its parameters, and generate it locally. If you need to keep the result, encrypt it in the browser before it is sent to the account vault. Each step is visible; nothing silently becomes a server-side key service.

  • Browser-side generation with the Web Crypto random source
  • Email plus one-time activation code; no card form in the activation flow
  • A personal vault that stores encrypted payloads, not a readable password list

What is live today

The running service includes an activation API, administrator-issued codes, sessions, basic administration and user-owned vault records. The generation workspace supports passwords, random-word passphrases, numeric PINs, machine tokens, recovery-code batches, Wi-Fi passphrases and UUID v4 identifiers.

  • Administrators can issue and revoke unused activation codes
  • Users can create, unlock and delete their own encrypted vault items
  • Account sessions and vault records are persisted in PostgreSQL

What we will not imply

A broad catalog is not a substitute for real cryptography. Blockchain wallets, post-quantum keypairs, organization-wide SSO, SCIM provisioning, billing automation and managed key custody are not presented as working capabilities unless and until they are implemented and independently verified.

  • No fabricated keypair or wallet-seed output
  • No claim of external certification or independent audit
  • No guarantee that a password generator replaces MFA or a dedicated password manager

A workspace for one person's real life

The same person may need a memorable phrase for a device, a random password for email, a network passphrase for a home router and recovery material for an account. Those outputs should not be conflated. Each profile explains what it creates, where it may fit and what the destination still has to do.

  • Start with the system that will consume the secret
  • Choose output format before choosing length
  • Keep account recovery independent from the account itself

The journey from first visit to daily use

A code is used once to create an account and set an account password. Later visits use an ordinary email-and-password sign-in. The generated values stay out of the API unless you explicitly save one; saving encrypts it in the browser before vault storage. The service still needs account and session data to provide that workflow.

  • Activation codes are issued separately by an administrator
  • No credit-card details are requested in the activation flow
  • The code does not prove mailbox ownership: email verification is not currently implemented

A sensible boundary for high-value secrets

A browser-based generator is useful for everyday credentials, not a substitute for a hardware signer or a reviewed custody setup. The device can access the value while it is visible, and an extension or malicious script could observe it. Use specialist software for wallet seeds, signing keys or assets whose loss would be irreversible.

  • Do not paste wallet seed phrases into a general website
  • Verify an output using the destination's official tooling
  • Use hardware-backed custody where the threat model requires it

Security is a workflow, not a label.

Review the implementation boundaries