Contact

DevsBox is maintained by a small team at inovisum. The fastest way to reach a maintainer is by email at hhammoud@inovisum.com. Most non-urgent messages are answered within two business days; security or privacy-sensitive reports are prioritized ahead of feature requests. The maintainer reads every message personally — there is no support inbox autoresponder and no ticketing portal.

When sending a message, please include the URL of the page involved, a short description of the input you pasted (redacted if it contains secrets), and the browser and OS you were using. Screenshots help when a layout looks off. Concrete reproduction steps make it possible to ship a fix on the next maintenance pass instead of guessing at what went wrong. If your bug involves a specific input — a JSON payload with an unusual escape sequence, a JWT with a non-standard claim, a regex that hits a catastrophic-backtracking edge case — please include a minimal reproducer that does not include any secret material.

Common reasons people get in touch:

• Bug reports. A tool produced the wrong output, threw an error, or did not handle an edge case (large inputs, unusual encoding, a specific RFC corner).
• Tool requests. A small utility you wish existed here. Single-purpose, paste-and-copy tools are the best fit for this site.
• Privacy and data requests. Questions about analytics, advertising cookies, or how to manage personalization in Google Ads Settings.
• Advertising concerns. An ad that looks broken, irrelevant to a developer audience, or potentially against Google's ad policies.
• Content corrections. A factual or technical error in any of the documentation around a tool, including the FAQ or example panels.
• Partnership or embedding. Using a DevsBox tool inside an internal developer portal or an onboarding workflow.

For privacy-related requests (data access, deletion, opting out of personalized advertising) the same email address routes to the maintainer responsible for compliance items. Please use a clear subject line such as “Privacy request” so the message can be queued correctly. The maintainer will not add anyone to a mailing list, share email addresses with a third party, or send marketing in response to a support thread.