We build the whole thing. Schema, API, admin, front end. Some parts are miserable to retrofit: authentication, permissions, background workers, audit trails. Those get designed on day one instead of bolted on the week before launch.
Taking two projects for Q4 2026
We build the software, then we keep it standing.
Pntix is a five-person engineering studio in London. We take a product from the schema up: web, mobile, and the servers underneath. Then we stay on after launch, because that is when the interesting problems start.
What we build on
0
Entries one live draw takes
GiveawayHub
0
Major build at a time
By choice
0
Engineers, no account managers
In-house
§ 01 · CAPABILITIES
Four things, done properly.
We would rather turn a brief down than take it on with a team we have to invent. This is the whole list.
Cross-platform where it saves you money, native where it does not. Offline-first data, push, in-app purchases. And the release plumbing that gets both stores to approve on the same afternoon, which is the part nobody budgets for.
Authenticated penetration testing. Dependency and supply-chain review. Rate-limit and abuse modelling, secrets rotation. What lands on your desk is a report with reproduction steps and a fix priority. Not a scanner dump.
Containerised builds, staged environments, migrations that roll back. Logs in one place. Alerts that page a human only when a human is needed. Cloudflare in front. Backups we verify the only way that counts, by restoring them.
§ 02 · SELECTED WORK
One project, in production, that you can open right now.
No mock-ups. No case studies for products that never launched. If it is on this page, it is on the internet.
§ 03 · HOW IT GOES
Four stages. You can leave after any of them.
You keep the architecture document whether or not we build it. That keeps both of us honest.
01
Scope call
Forty-five minutes. We map what you actually need against what you think you need, then say which parts we would cut.
02
Architecture
A written plan. Data model, services, hosting, cost per month. You keep it whether or not you hire us.
03
Build
Two-week increments against a staging URL you can open whenever you like. No demo theatre. No surprise reveal at the end.
04
Handover
Runbooks. Credentials in your name, not ours. A security pass, and a month of support while your team settles in.
§ 04 · THE TEAM
Five people. You will work with all of them.
No delivery layer sits between you and the person writing the code.
Mahmoud Glala
Chief Executive Officer
Kareem Rihan
Head of Frontend
Mahmoud Emad
Head of Backend
Muhammad Ashraf
Design Director
Ahmed Mohamed
Security Director
§ 05 · START HERE
Tell us what breaks, and when.
Pick a date and a calendar hold lands within one working day. Forty-five minutes. No deck, no salesperson. You get the engineer who would run the build.
Request a scope call
Five fields. We reply to every one of them.
Booked into the queue.
One of us reads this within a working day and comes back with two time slots. If it is urgent, use WhatsApp. It is faster than waiting on us.