A dozen apps show you a map.
We show you what's behind it.

Yes. AI was used to write code, and we don't shy away from that. We'd rather be upfront and honest about it than have you wonder.

What we'd rather talk about is what that code had to survive before it reached your phone: a written specification approved before anything was built, a failing test written before every fix, 2,639 automated tests and a strict type check that must pass, a numbered and reversible migration for every database change, security policies proven against the live database, and a server-side switch on every feature so it can be turned off in seconds.

So judge us on that bar rather than on who or what typed the code. A tool that writes code faster doesn't lower the bar. It just means more gets built against it.

“Vibecoding” means accepting generated code without reading it, testing it, or understanding it.

Here's what that method cannot produce. 150+ numbered database migrations, each with a verification query and a rollback script, logged in order. 33 server-side functions with their own test suites. Row-level security policies proven against production, table by table. Native home-screen widgets for both iOS and Android, and a CarPlay app written in Swift. 31 written feature specifications. An audit checklist that grows every time human judgement catches something the tests missed.

None of that survives a process without gates. Judge the result by the app.

The government feeds are where the prices come from, and we say so plainly: eight of them, one per state and territory. Every serious fuel app in Australia uses them, and any app claiming otherwise is worth a second look.

They're also where most apps stop. A government feed won't tell you whether a station is open at 11pm, whether it sells AdBlue, what its phone number is, or what your RAA membership actually takes off the price at that specific site. That layer is ours to build, and it's 33 scheduled jobs deep: opening hours for 5,317 stations, phone numbers for 2,495, AdBlue availability, and six motoring-club discount programs applied as real cents per litre.

We don't sell it, and we don't run ads.

Usage analytics are pseudonymous: at most a random account identifier, never your email, your name, your precise location, or anything you type. There's no session recording, and nothing is captured automatically. Events come from a fixed list written into the code, not a blanket record of every tap. You can turn analytics off in Preferences, and you can do that without an account, because a privacy control that requires signing up isn't a privacy control.

Everything stored against your account sits behind row-level security policies that we test against the live database to prove one account cannot read another's. You can delete your account and your data from inside the app.