This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Maskink
Redact logs before AI sees them, restore values in the reply
Maskink replaces passwords, keys, IPs, hostnames and names in logs, scripts and chats with consistent placeholders. The AI sees only tokens; you read the reply with real values. Self-hosted, 95 editable rules, and a JSON API for your own apps. Interactive Demo: https://spaksu.github.io/maskink
AI is great at reading logs and scripts, but those files are full of passwords, internal IPs, server names and people's usernames. Cleaning them by hand is slow, and you lose track of which server was which. So I built Maskink.
It swaps sensitive values for consistent placeholders:
mysql -u app_user -p'S3cr3t!2024' -h db01.corp.local
mysql -u <USER_2> -p'<PASS_1>' -h <FQDN_1>
The same value always gets the same token, so the AI can still reason about what happened where. When the reply comes back, the tokens turn back into your real values.
Three things I focused on:
Small: PHP and MySQL. No Composer, no build step, no CDN. It runs without internet.
Easy to integrate: POST text to a JSON endpoint from any language and get the masked text plus the mapping. PHP apps can use the engine class directly.
A serious rule set: 95 built-in rules across 19 categories, covering network device configs, Windows and Linux logs, cloud tokens, PEM keys, plus checksum-validated cards, IBANs and Turkish IDs. Every rule can be edited, tested live or replaced with your own.
It also has a masked AI chat that works with Ollama, vLLM or any OpenAI-compatible endpoint, and it can cover sensitive text in screenshots using local OCR.
Masking is rule-based, so no rule set catches everything. Please review the output before sending anything sensitive.
It's MIT licensed. I'd love your feedback: which log format or token should it catch that it doesn't today.
About Maskink on Product Hunt
“Redact logs before AI sees them, restore values in the reply”
Maskink was submitted on Product Hunt and earned 6 upvotes and 3 comments, placing #32 on the daily leaderboard. Maskink replaces passwords, keys, IPs, hostnames and names in logs, scripts and chats with consistent placeholders. The AI sees only tokens; you read the reply with real values. Self-hosted, 95 editable rules, and a JSON API for your own apps. Interactive Demo: https://spaksu.github.io/maskink
On the analytics side, Maskink competes within Open Source, Privacy, Artificial Intelligence and GitHub — topics that collectively have 605.6k followers on Product Hunt. The dashboard above tracks how Maskink performed against the three products that launched closest to it on the same day.
Who hunted Maskink?
Maskink was hunted by Safa Paksu. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Maskink including community comment highlights and product details, visit the product overview.
Safa Paksu
Hi Product Hunt, I'm Safa.
AI is great at reading logs and scripts, but those files are full of passwords, internal IPs, server names and people's usernames. Cleaning them by hand is slow, and you lose track of which server was which. So I built Maskink.
It swaps sensitive values for consistent placeholders:
mysql -u app_user -p'S3cr3t!2024' -h db01.corp.local
mysql -u <USER_2> -p'<PASS_1>' -h <FQDN_1>
The same value always gets the same token, so the AI can still reason about what happened where. When the reply comes back, the tokens turn back into your real values.
Three things I focused on:
Small: PHP and MySQL. No Composer, no build step, no CDN. It runs without internet.
Easy to integrate: POST text to a JSON endpoint from any language and get the masked text plus the mapping. PHP apps can use the engine class directly.
A serious rule set: 95 built-in rules across 19 categories, covering network device configs, Windows and Linux logs, cloud tokens, PEM keys, plus checksum-validated cards, IBANs and Turkish IDs. Every rule can be edited, tested live or replaced with your own.
It also has a masked AI chat that works with Ollama, vLLM or any OpenAI-compatible endpoint, and it can cover sensitive text in screenshots using local OCR.
Masking is rule-based, so no rule set catches everything. Please review the output before sending anything sensitive.
Interactive Demo: https://spaksu.github.io/maskink
It's MIT licensed. I'd love your feedback: which log format or token should it catch that it doesn't today.