Interfaces built the way
we wanted to find them.
Aurelius Black makes complete interface systems for Next.js and React. 20 products, one design system, and a deliberate refusal to ship the half of an interface that usually gets skipped.
Because buying a template used to mean buying a screenshot. You would pay, download, open it, and find the dashboard was one page, the table broke past two hundred rows, the empty states did not exist, and the whole thing was built against a framework version that had moved on twice.
Meanwhile the parts that actually take the time, the states, the edge cases, the density decisions, the moment a metric goes negative, were left as an exercise for the buyer. That is the expensive half. Leaving it out is what made templates feel like a shortcut that doubled back on itself.
So the standard here is different: a product is finished when a sceptical developer can click through the deployed demo, go hunting for the thing we skipped, and not find it.
A screen is not finished until its failures are drawn
Most interface work stops at the happy path. But the first thing a real user meets is an empty state, and the thing they remember is what happened when something broke. Every product here ships its empty, loading, partial-failure, permission-denied and filtered-to-nothing states, with copy that says what to do next rather than that something went wrong.
Density is a design decision, not an accident
An operations console read under time pressure needs different density from a marketing page read on a sofa. We pick deliberately, per product, and we ship a compact mode where the job demands one. Generic templates default to comfortable and leave professionals to fight it.
One system beats twenty folders
Every product shares the same tokens, spacing scale and component contracts. A pattern learned in one is the same pattern in the next, which is why the second thing you buy from us costs you almost no learning time.
Show the thing, do not describe the thing
Every product has a real deployed demo, linked from its page, with no form in front of it. If a product cannot survive being clicked through by a sceptic before payment, it is not finished.
- Ship a product whose demo we would not let a sceptic loose on.
- Sell a licence and then charge again for the updates that keep it working.
- Phone home, check licences at runtime, or put an activation server between you and files you paid for.
- Pad the catalogue with thin products to make the range look bigger.
- Make a refund harder than it needs to be, or hide the policy behind a menu.
The files work whether or not you paid. That is deliberate. We would rather trust customers than inconvenience them, and the licence is written the same way.
Go and look at one.
That is the whole argument. Everything above is just words until you have clicked through a demo.