About MockLane

Why it exists

The parts of an application that are hardest to test are the parts you do not control. A payment provider's webhook only fires against a public URL. An API your team has not written yet cannot be called. An email is either sent to a real person or not sent at all.

The usual answer is three separate tools, three accounts, and glue code in between that nobody owns. MockLane exists because those three problems show up in the same afternoon, on the same feature, and the interesting part is where they meet — replaying a captured payload into a mock, or asserting that the email actually arrived.

How it is run

It is a small, independent product, not a venture-funded one. In practice that means a few things we would rather say out loud than have you discover:

• Quotas are hard limits, not billing thresholds. You cannot run up a bill you did not choose.
• We publish what the product does and not what it might do. When a competitor is the better fit, the Why MockLane page says so.
• Support is a real inbox, read by the people who build it. There is no ticket portal and no phone queue.

Getting in touch

Support, billing, security reports and anything else go to info@mocklane.com. There is more detail on the contact page, and the privacy policy sets out exactly what data the service holds.