layercell.com
Small, sharp tools that each do one thing, and tell you exactly what they did.
We build B2B software for teams running Shopify stores, Stripe accounts and GitHub repositories. Every app will install in two steps or fewer, state each permission it asks for in plain words, and bill monthly with no contract.
Nothing is on sale yet. This page exists so you can see how we intend to build before we ask you for anything, and so there is a real address behind the name.
The mark
Amber names the platform. Grey is the app's fingerprint.
Every app shares this header, this footer, this type scale and these nine colours. What changes is the field, and it uses two materials because it says two things. One row is amber end to end: that row names the platform, it is the only complete amber row, and you can read it at favicon size. The grey cells outside it are derived from the subdomain itself — a fingerprint, not a code. You are not meant to decode the grey, only to notice that two apps differ and both are ours.
layercell.com — nothing lit. The whole field is the family.
Amber row 1 — an Atlassian app. Grey cells are its fingerprint. Illustration; the first app is still in build.
Amber row 3 — our own operations console. Same system, different row.
Amber row 1 — Atlassian
Jira and Confluence. Claimed 2026-07-30, first product out the door
Amber row 2
Goes to the second vendor to receive a product, not to the next one we would like to build for
Amber row 3 — internal, and the third vendor
Our own operations console sits here; it is not a vendor and never competes for a claim
A mark is computed from its subdomain, so a new app needs no colour, no coordinate and nobody's permission — and no existing mark ever changes. A row is claimed when a vendor receives a product, in the order products ship, because three rows exist and reserving one for a platform we merely intend to build on spends it on software that does not. There is one accent for the whole portfolio, which means nothing has to be memorised and nothing fails for a colourblind reader.
How we build
Four commitments, the same in every app.
Every permission is explained before you grant it
The install screen lists each scope we request and why we need it, in the words a shop owner would use. We never ask for a scope we do not read.
Nothing happens silently
Every write we make is in a log you can read, filter and export. If a run fails you are told what failed and when we will try again.
Cancel from settings, not from an email thread
Monthly billing, no contract, no cancellation call. Your data stays exportable for thirty days after you leave.
We stay out of the way inside your dashboard
Embedded screens use each platform's own components, so an app looks like the dashboard it lives in. This brand belongs to our own pages only.
Tell us what you are doing by hand
We build tools for jobs we can finish, and we will say so plainly if yours is not one of them.