📢 Welcome to CarryPass Discussions!

[racz-zoltan]

Welcome to the official discussion space for CarryPass!

CarryPass is a privacy-first, client-side credential manager and small-team credential sharing tool. It runs in the browser as an offline-capable PWA, with no accounts, no telemetry, and no server-side state.

This space is for questions, feedback, bug reports, security observations, feature ideas, usability comments, and discussion around the project’s architecture.

---

🔐 What CarryPass focuses on

• Client-side operation — cryptographic operations happen in the browser
• No accounts or central authority — CarryPass does not rely on a server-side identity system
• Deterministic password generation — passwords can be regenerated from the same personal key and service settings
• Adaptive icon path login — a strong passphrase is combined with a chained visual icon sequence
• Encrypted team vaults — admins can distribute encrypted static vault files for small teams
• Trusted-device onboarding — QR-based enrollment for member access
• Offline-first PWA — installable and usable after first load
• Self-hostable static deployment — teams can host their own copy and vault file
• Open source — MIT licensed

---

💬 Suggested discussion topics

• 💡 Feature suggestions
• ❓ Help and questions
• 🐞 Bug reports
• 🔐 Security feedback
• 🧪 Usability testing
• 🧱 Architecture and self-hosting
• 🌍 Translations and documentation

---

⚠️ Project scope

CarryPass is not intended to replace enterprise password managers, SSO/IAM platforms, or centrally audited access-management systems.

It is designed for users and small teams who want a privacy-first, stateless, client-side way to generate and share credentials without creating accounts or storing secrets on a server.

---

🔗 GitHub: https://github.com/racz-zoltan/racz-zoltan.github.io
🌐 Website: https://carrypass.net

Please keep the discussion constructive, respectful, and specific. Security feedback is especially welcome.