01
Web engineering
Custom systems, not assembled templates.
- Custom React + Next.js
- Python backends
- PostgreSQL at scale
hello @ atellius.com
Atellius — Studio & Engineering / Est. 2026
Custom React, Next.js, and Python systems for teams who can tell the difference. GEO, AEO, and AIO services for AI-era visibility.
What we do
Engineering
React, Next, Python, Postgres, Cloudflare — built without templates.
Visibility
GEO, AEO, AIO. Be cited by the systems that replaced the search box.
Pipeline
Inbound that converts because it was triaged, enriched, and qualified.
Performance
LCP < 1.5s on throttled mobile. Enforced in CI, not aspirational.
Why us / 02
No shadcn, no Lucide, no Tailwind UI, no Framer presets. Every component is written from scratch in the file that ships. A Wappalyzer scan returns Next.js and React — and nothing else. That is the authorship fingerprint, and it is non-negotiable on every site we ship.
The person on the discovery call is the person writing the code. No agency layer, no offshore subcontractor, no “senior” who hands the build to a junior team. Every commit on every project is signed by someone you have spoken to directly.
We own and operate geo.atellius.com — the same scanner that audits client sites is the scanner agencies white-label from us. AI-search visibility is not a service we resell. It is infrastructure we built, run, and ship into every site we hand over.
LCP under 1.5s on throttled mobile is a build-gate, not an aspiration. Lighthouse SEO 100 ships on every page or the deploy fails. Real-device numbers, real thresholds, written into the pipeline before a client ever sees the site.
Selected work / 01
How we work / 03
Two-week fixed-scope read of the existing system. For a website: GEO + AEO + performance scan, full Lighthouse + real-device pass, schema and entity-authority gap analysis, and a written brief on what to keep, kill, and rebuild. Deliverable: a 24-page PDF and a kickoff call. No discovery phase that bills for six months of slide decks.
One page of architecture, written before any code. Stack choices, data model, deployment topology, third-party integrations, billing model if applicable. Reviewed with you on a single call. Signed off before week three. No “sprint zero” that runs three sprints long.
Hand-coded in the file that ships. Weekly demos on a staging URL you can open from your phone. No design-then-development handoff — the person designing the component is the person writing it. You see the work as it exists, every week, in production code.
Performance budgets enforced in CI before merge. Schema and GEO checks re-run against the new build. Real-device Lighthouse pass on throttled mobile. Every claim on the marketing site is mapped to a proof point in the codebase or it does not ship.
Production deploy on a Cloudflare edge, with rollback in one git revert. You get the code, the deploy pipeline, the analytics, and a written handover. Future-legible by design — no proprietary CMS, no licence we control, no rebuild required in eighteen months.
Clients / 04
Atellius built the public tools and the paid program portal as one system. A reader can run the BMI calculator, buy a program, and land inside the member area without a second login or a redirect to some third-party course host. The auth, the billing, the program delivery — it is all on the same domain, written for my content rather than retrofitted around a template. That is what I asked for, and that is what they shipped.
More references on request — additional named quotes ship as current retainers close their first quarter.
/ stack — what we work in
Services / 02
We engineer the systems, we make them visible to the AI engines that decide who gets cited, and we sort the inbound that follows. The same studio. The same craft bar.
01
Custom systems, not assembled templates.
02
Be cited by the systems that replaced the search box.
03
Inbound that converts because it was sorted.
SEO optimises for the ten blue links. GEO optimises for the systems that replaced them — ChatGPT, Perplexity, Google AI Overviews, Claude. The work overlaps on technical foundations (schema, crawlability, entity authority) but diverges on output: SEO chases rank, GEO chases citation frequency.
Fixed-scope projects start at four weeks for a single-purpose build (audit, landing system, triage widget) and run six to twelve weeks for a full site or platform rebuild. Studio retainers are monthly, with weekly demos and a fixed scope per month. No open-ended hours.
We write it. There is no agency layer, no offshore subcontractor, no white-labelled junior team. The person on the call is the person on the keyboard.
Because a Wappalyzer scan should not be able to tell you who built our work. Hand-built primitives are the authorship fingerprint — and the only honest answer to a client paying studio rates for studio work.
Usually yes. We default to React, Next.js, Python, Postgres, and Cloudflare because that is what we ship fastest, but we have rebuilt platforms off WordPress, Webflow, Squarespace, and bespoke legacy stacks. The stack is a means, not an ideology.
A fixed-scope 24-page PDF audit, scored across eight AI-visibility dimensions, with a per-finding remediation plan a developer can ship from. Turnaround is under 24 hours from kickoff. Pricing is on the service page — no “contact us”.
Studio is based in India. Clients ship from the US, UK, UAE, and India. Async-first, scheduled calls when needed, weekly demos on every retainer.
Studio note / 03
So much of what ships in 2026 is the same shadcn page with the same Lucide icons and the same three-column feature grid. It compiles. It deploys. It does not feel like anything.
We build the way we were taught to: from scratch, in browser, with the cursor on the line that matters. The result is sites that hold attention because someone obviously held it while writing them — and that perform because every choice was an actual choice.
If a Wappalyzer scan tells you who built our work, we did not build it.
— Nawab Islam, Studio Lead