Skip to content
All posts
Company 8 min read

What we learned auditing two competing platforms

We read the products properly before building. The findings changed our architecture.

Ft

Founding team

Company ·

Before writing a line of product code, we spent a week auditing two established platforms in this category — with authorised accounts, read-only, on our own data. Three findings changed what we built.

1. Administrative routes rendering to ordinary accounts

On one platform, a business customer account rendered the full reseller and administrative interface — customer lookup, margin rules, domain settings. The API correctly refused the data, so nothing leaked. But the structure, field names and capability were all visible.

This is a presentation-layer problem, not a breach. It still shaped us: a permission you lack should remove the route, not just empty it. That is why our navigation is derived from a registry rather than authored.

2. State-changing GET requests

A link that looked like navigation changed an account setting. Our read-only crawler followed it and altered a preference on our own test account — exactly what a browser prefetcher, an antivirus link scanner or a chat preview would do.

GET must be safe

If clicking a link can change state, any well-behaved tool that follows links will change your state. This is not a hypothetical.

3. Pagination that was not there

Of 126 routes on one platform, five had pagination controls. The reseller's own customer list — the screen most likely to grow large — had none. We now apply server-ready pagination to every list from the start.

What we did not do

Copy anything. The audit was to understand the domain and the constraints, not the interface. Our palette, geometry, component system and architecture are original, and we deliberately did not keep screenshots around while designing.

Get the next one

One email a month with new posts and notable product changes.

More posts