A serverless distributed hash-cracking platform built on AWS, offering pay-as-you-go GPU power with an intuitive UI.
NPK is a distributed hash-cracking platform built on serverless AWS components that provides on-demand GPU power for password recovery and security testing. It solves the problem of expensive upfront hardware and electricity costs by offering a pay-as-you-go model, allowing users to scale cracking power as needed while minimizing idle expenses.
Security professionals, penetration testers, and red teams who need efficient, scalable hash-cracking capabilities without investing in physical hardware.
Developers choose NPK for its cost-effective, serverless architecture that eliminates hardware management, its intuitive UI that simplifies complex cracking campaigns, and built-in safeguards against runaway cloud costs.
A mostly-serverless distributed hash cracking platform
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Deploy with a single command in AWS CloudShell, as shown with the one-liner installation, making setup quick and accessible even for non-experts.
Intuitive UI simplifies creating complex hash-cracking campaigns with a few clicks, reducing the need for deep Hashcat expertise, as highlighted in the features.
Provides pre-execution cost and coverage estimates, and enforces maximum price limits with runaway instance protection, ensuring predictable budgeting and safety.
Supports multi-tenancy with strict data separation and optional SAML SSO, enabling secure team use as described in the multi-user administration section.
Built entirely on AWS serverless components like Cognito and DynamoDB, making migration to other clouds or on-premises difficult and creating dependency risks.
Strongly recommends deployment in a new AWS account, which can be inconvenient for organizations with existing infrastructure and adds management overhead.
Advanced settings and configurations are linked to an external wiki, potentially leading to less integrated or outdated information compared to in-repo docs.