Contact Layerbit
A bug in a tool, an error in a guide, a request for a utility that does not exist yet, or an enquiry about engineering work — all of it reaches the same small team, and all of it is read.
The best route for anything with detail: bug reports, corrections to a guide, tool requests, and enquiries about custom engineering work.
ceo@layerbit.co.inUseful for a quick question or an initial conversation about a project, where a back-and-forth is faster than email.
Start a chatWhat to include, by type of message
None of this is required — a one-line message is fine and we will ask if we need more. But if you already have the details to hand, including them usually saves a round trip and gets the problem fixed in the first reply rather than the third.
A tool is behaving wrongly
The most useful thing by far is input that reproduces it — with anything sensitive replaced by dummy values that still trigger the bug. Add which tool, what you expected, what happened instead, and your browser and version. Most parser bugs come down to one specific character in one specific position, and without a sample we are guessing.
A guide has an error
Please tell us. Technical writing that is wrong is worse than no writing at all, and we would rather correct it than leave it standing. Quote the sentence and say what it should say — a specification reference is welcome but not necessary. Corrections get made and the page's modified date updated.
A security issue
Put [SECURITY] in the subject line and describe the issue and how to reproduce it. Since the tools run entirely in your browser and we hold no accounts or user data, the realistic surface is things like a cross-site scripting vector in how a tool renders your input — which we treat seriously and fix first.
A tool that should exist
Tell us the task, not just the tool name. "I keep having to diff two JSON objects and ignore key order" tells us far more than "add a JSON diff", because the real requirement is usually narrower and more specific than the generic tool would be.
Engineering work
A paragraph on what you are trying to achieve, roughly when you need it, and any fixed constraints — existing stack, systems it must integrate with, compliance requirements. We will tell you honestly whether it is something we are a good fit for, including when the answer is no.
Using a tool in your business
You do not need our permission to use the tools for commercial work — they are free for that, and no attribution is required. Do get in touch if you need something beyond that, such as a self-hosted copy running inside your own network.
Who you are contacting
Layerbit Technologies is an independent software studio based in the United Arab Emirates. It builds and maintains the free browser-based developer tools on this site, and takes on client engineering work — API automation, ERP systems, application development, static site delivery and portfolio design.
There is no call centre and no ticketing system. Messages go to the person who writes the code, which means replies are not instant but they are informed. If you are asking why a particular tool made a particular decision about your data, you will be answered by whoever made that decision.
For how the site handles data and cookies, see our privacy policy. For the terms covering use of the tools, see the terms of service. Background on how and why the site is built the way it is lives on the about page.
Frequently asked
Usually within one to two business days. We are a small independent team rather than a staffed support desk, so we would rather give you an accurate expectation than promise a four-hour turnaround we cannot consistently meet. Messages marked [SECURITY] are looked at first.
No. There is no sign-up, no login and no account system anywhere on the site, and no plans to add one. Every tool works immediately on first visit, and nothing is stored against you because there is no "you" from the site's point of view.
For every tool except LayerLink, your input is processed entirely in your browser and never transmitted, so you can verify this yourself in your browser's network tab, or simply go offline and keep working. That said, your own organisation's policies are the ones that govern what you may paste into a web page, and we would always rather you check than assume.
Yes. Layerbit takes on engineering contracts, most often API and workflow automation, internal tooling, ERP integration work, and static site delivery. Email is the best starting point, with a short description of what you need and your rough timeline.
Email a description of the task you are trying to do. We build tools for problems we can see clearly, and a concrete account of your actual workflow is far more useful than a tool name — it often reveals that the useful tool is a slightly different one from the one requested.
In September 2026 we removed three utilities that depended on third-party APIs for breach data, URL reputation and IP geolocation. They relied on services we did not control, could stop working without notice, and required sending your input to another provider — which conflicts with the promise the rest of the site makes. We would rather offer fewer tools we can stand behind completely.
Changelog
- v1.3.0 Rewrote this page around what to include in each kind of message, and replaced the enterprise SLA language with the response times we can actually honour.
- v1.2.0 Added guidance for security reports and guide corrections.
- v1.1.0 Added WhatsApp as a second contact route for quick queries.
- v1.0.0 Initial contact page.