Not brochure sites. ERP, hospital management, HR and payroll, point-of-sale and banking — platforms in production, built and maintained by one team across Dhaka and Toronto.
export const requireCompanyContextScope = (request: any): string => { // The RolesGuard resolves the active company AND confirms // the caller's membership, then stamps the validated id onto // the request. Trust THAT — never re-derive tenant scope // from a forgeable cookie. const stamped = asSingleValue(request?.activeCompanyId)?.trim() if (stamped) return stamped const header = asSingleValue(request?.headers?.['x-company-id']) const cookie = asSingleValue(request?.cookies?.[activeCompanyIdName]) if (header && cookie && header !== cookie) throw new BadRequestException( 'Company scope mismatch between context cookie and header.' ) const companyId = header ?? cookie if (!companyId) throw new BadRequestException( 'Company context is required. Set an active company first.' ) return companyId} Government, banking, healthcare, HR and payroll, retail and hospitality.
Next.js on the web, React Native for iOS and Android, and Rust with Tauri on the desktop — all three on one API, in NestJS or .NET.
ZettaByte Technology Limited, Dhaka. ZettaByte Technology Inc., Toronto.
In every platform we ship
Tested on every commit.
You see it before we do.
Field-level, re-checked server-side.
Who changed what, a year on.
No refresh button.
Long work off the request.
ZettaByte is a product engineering company, not an agency that hands a project on at launch.
The work started in Dhaka and now runs from two offices and two registered companies: ZettaByte Technology Limited in Bangladesh and ZettaByte Technology Inc. in Canada. Same team, same codebase, two time zones.
These are the systems we build, and every one of them stands on the same foundations — tenancy, permissions, audit, billing — written once and already running in production under the platforms we have shipped. A project that matches one of these does not start from an empty repository.
Choose a foundation to see everything built on it, or a platform to see what it is built from
Don't see yours? Most of what we build is custom anyway — the platforms just mean we have probably solved half your problem already. Tell us what you need →
Three reasons, none of which are adjectives.
Most agencies begin every project at zero; we usually begin at version one. You pay for the part that makes your business different, not for rebuilding the tenancy, the permissions and the audit trail that every system of this kind needs and no client ever sees.
ZettaByte Technology Limited in Dhaka and ZettaByte Technology Inc. in Toronto. Whichever market you are in, you contract with a company registered in it — a local invoice, under law you already work under, rather than an offshore supplier agreement.
Nothing is handed to a junior after the pitch, nobody learns on your budget, and there is no account manager who has to go and ask someone else. The same people stay with the system afterwards, so whoever picks up the phone two years later already knows why it was built that way.
One working day, both offices
Dhaka is 10 hours ahead of Toronto today, so an ordinary working day in one sits across the night in the other. A question asked at the end of yours is picked up 6 hours later at the start of ours — which is still the same night where you are. Nobody is working unusual hours; the planet is doing it.
Toronto
ZettaByte Technology Inc.
Dhaka
ZettaByte Technology Limited
Toronto time
Toronto works 9 to 18 in its own time. Dhaka's working day begins at 09:00 local, which is 23:00 in Toronto —6 hours after a question asked at 17:00.
Six stages, three-week sprints. At the end of every sprint you get working software you can click through — not a status report. Below: what we take on, and what we build it with.
The work, between the conversations
Deployment, data migration, and training your team so nobody is guessing on day one.
The last three steps are the ones that repeat. A system a business cannot switch off is not finished at launch — it is fixed, deployed and fixed again, by the people who built it.
What we do
If it is not here, we will tell you honestly and point you at someone who does it well.
The stack, and why
When you eventually bring engineering in-house, you will be recruiting for skills people actually have.
| Layer | Choice | Why |
|---|---|---|
| Interfaces | Next.js | Server-rendered pages that load fast and are readable by search engines, without giving up a modern React codebase. |
| APIs | NestJS | Structure enforced by the framework, so a backend still makes sense at fifty thousand lines and a new engineer can find things. |
| Mobile | React Native | One codebase for iOS and Android, sharing types and business rules with the web app so a change to a calculation does not have to be made three times. |
| Desktop | Rust + Tauri | Native desktop apps for Windows, macOS and Linux. Tauri uses the system webview instead of bundling a browser, so builds ship in megabytes rather than hundreds of them, and the Rust core handles the work that has to be fast and cannot crash. |
| Data | PostgreSQL | Your data will outlive every framework decision on this page. Postgres is the one choice here we would still make in ten years. |
| Schema & migrations | Prisma | Schema changes that are reviewed, versioned and reversible, rather than someone running SQL against production by hand. |
| Caching & queues | Redis | Background jobs and cached reads, so the slow work happens away from the request the user is waiting on. |
| Deployment | Docker | What we test is what you run. The same image moves from a laptop to staging to production. |
And .NET
The table is what we reach for on most builds. .NET is the other stack we ship on: Zetta Commerce, our online shop platform, runs its API on ASP.NET Core, with EF Core over PostgreSQL. Where the environment is already Microsoft — an existing .NET codebase, SQL Server, IIS, or a procurement rule that requires it — we build on .NET too. C# is where this team came up: the oldest repositories on our GitHub are C# from 2015, and they predate every JavaScript entry above.
Two of them are public: dotnet-cms-api, a REST API on .NET 10 with EF Core, JWT auth and Swagger, and devgo-winforms, the first version of DevGo — a Windows desktop tool in C# before it was rebuilt in Rust.
Everything above this line is what we say. Everything below it is checked: live client systems, the screens they actually show, two figures read from our commit history and from asking those systems whether they answer, and the people who commissioned them, quoted as sent.
The systems
Every card opens the real thing, at the address it answers on.
3
Systems we built that a client now runs.
9
Ours, built and run by ZettaByte.
3 of 6
Working builds you can click through.
Measured, not written
Changes in ninety days
419
Last shipped .
The area of each change is shown, not the message — those are written for us, not for you.
Systems answering
12/12
responding when this page was built
Checked , when this page was last built. It is a reachability check, not an uptime percentage — we would rather publish the smaller number we actually measure than a figure over a window nobody recorded.
In their words
Reproduced as they arrived, sign-offs and all — beside the state of the system each one is about.
The Banani DOHS review is also on clutch.co, collected and verified there rather than by us.
ZettaByte built our website and our community mobile app, and we are very happy with both. We were so impressed with their communication and commitment that we are now having them fix our HR system, and we plan to give them more work in the coming days. Best wishes, Team Zetta.
01
Website and community mobile app
ZettaByte communicated well, understood our requirements, and delivered what they promised. They respond quickly when we need changes or support.
Answering when this page was built, just now. A reachability check against the client’s own address, not an uptime figure.
A vendor who assembles fails differently from one who builds. Both of these run on the machines this company works from every day: a provisioning menu that reads a fresh machine and installs what it is missing, and a menu bar inside Neovim with its own training wheels — labelled, so they can be taken off.
$ zetta setup
Machine state: sample3 of 5 installed
The two people who answer for the work, in their own words. Both are reachable at the addresses on this page.
We build lasting partnerships, not deliverables. I’m proud of what we’ve shipped, and more interested in what comes next — a way of working where technology doesn’t just support a business but moves it forward. Being part of this team is something I’m genuinely proud of, and I’m glad you’re here to see where it goes.
I built the foundation our platforms stand on — tenancy, permissions, audit and payroll, written once and running in production underneath all of them. When a client asks who designed the system they’re buying, the answer isn’t a department, and I’ll walk you through any layer of it.
Notes on the things we keep being asked about — what a platform costs to run, why a data model is the expensive decision, and what actually breaks in year two.
No Posts available.
You do not need a specification, or even a settled idea of scope — a question is a fine place to start. Below: the answers we give most often, the form, and both addresses.
Before you ask
Start here
Fill in the form and one of the two people above answers it. There is no sales team to route it through.
Or email us directly at info@zettabyteincorp.com
Your clients need software. We build it. Partner with ZettaByte
The addresses
Asia
North America
