Loading…
Software & automation studio
Web systems, mobile apps and operational software, built around how your organisation actually works. Repetitive work is handled by automation and AI.
Start from your problem
Write one sentence and see, right here, what we would build and where we would start.
Capabilities
Most engagements combine two or three. All of them are built to run in production for years, not to demo well.
Dashboards, portals, internal tools and customer-facing products. Server-rendered for speed, typed end to end, with roles and permissions designed before the first screen.
Next.js · TypeScript · PostgreSQL
Example: Web applications
The system a business actually runs on: order entry, production tracking, stock, purchasing, delivery and reporting — modelled on how your operation works rather than a generic template.
Inventory · Orders · CRM · Reporting
Example: Operational systems
Systems that do not talk to each other, made to. Scheduled jobs, document pipelines, approvals and hand-offs that run without anyone remembering to start them.
Integrations · Jobs · Webhooks
Example: Workflow automation
Assistants answering from your own documents with citations, data extracted from invoices and forms, semantic search that understands a question, and incoming requests routed on arrival.
RAG · Embeddings · Extraction
Example: Applied AI
Android and iOS apps that share one backend with your web system, so the floor, the office and the warehouse are looking at the same numbers.
iOS · Android · Offline-capable
Example: Mobile applications
Deployment, environments, backups, monitoring and scaling. Set up so a bad day is a rollback rather than an outage.
CI/CD · Monitoring · Backups
Example: Cloud & infrastructure
How we work
Nothing is built before the problem behind it is understood, and nothing is hidden until the end.
We map how the work moves today — who touches what, where it stalls, which systems disagree. You get a written picture of the process before anyone proposes software.
We decide the data model, the architecture and the screens together. Where a simpler answer exists — an automation instead of a platform — that is what we recommend, even when it is the smaller project.
Staged delivery in two-week increments, each one deployed and usable. The task causing the most pain ships first, so the work gets easier before the project ends.
The system is deployed on the agreed infrastructure. You get administrative access, documentation, and a training session for your team.
01
We map how the work moves today — who touches what, where it stalls, which systems disagree. You get a written picture of the process before anyone proposes software.
Process map · scope · estimate
02
We decide the data model, the architecture and the screens together. Where a simpler answer exists — an automation instead of a platform — that is what we recommend, even when it is the smaller project.
Technical spec · data model
03
Staged delivery in two-week increments, each one deployed and usable. The task causing the most pain ships first, so the work gets easier before the project ends.
Working increments · staging
04
The system is deployed on the agreed infrastructure. You get administrative access, documentation, and a training session for your team.
Production · docs · training
Projects
One sheet each: the need behind it, what was built, and its mechanism running right here.
Demand intelligence In development
You see the selling season before it arrives.
Commerce platform In production
Fifteen screens of the real product, redrawn, with nothing of the client in them.
Search by part name, OEM code, part number or car model.
SKU-1042Front brake rotor● 4 available online · max 2 per orderSKU-2210Oil filter● 12 available online · max 4 per orderSKU-3305Spark plugs (set of 4)● 6 available online · max 2 per orderNative desktop app Complete
Press the shortcut, speak, and the Persian text lands where you were typing.
Coaching platform In development
Each student's programme on the coach's phone, and a record that climbs week by week.
More
Commitments, engineering, stories, articles, examples and live figures — each opens with a tap.
Voice message to Mazarix
If you have no time or patience for a meeting, sign up and leave us a voice message of up to ten minutes about the website, app or work you want automated. Your voice is turned into text, its points are put in order, and it reaches our team. We look at what you need and answer you in the same conversation.
At Mazarix, even hearing what you need is automated.
Sign up with your email alone, no password
Our commitments
End-to-end delivery
Specification, architecture, build, deployment, hand-over.
You own the software and the data
The software, the data and the infrastructure are yours. We agree hosting with you per project, before the contract.
owner: youSecurity by default
Access enforced at the database, not just the app.
at the database, not only the appNo lock-in theatre
Defined scope, defined end. Support is optional.
Quality
Most of what software costs is paid after delivery — for the things nobody thought about while it was built. Each claim here shows its mechanism above the words.
Every change passes through an automatic set of checks before anyone sees it. What gets caught there never reaches you.
If your staff need a manual to use a screen, the screen is not finished. Each one has a single main job, in plain sight.
A page that takes four seconds is a page most people never scroll. Pages arrive already drawn.
Access is separated at the lowest layer, not in a screen. A mistake in a screen cannot show one customer's data to another.
For the technical reader: four stack choices with their reasons, the code behind each claim with line numbers, and the gates where you can break the build yourself. Not technical? Skip it — you lose nothing.
Engineering
Chosen because it is well understood and will still be maintained in five years — not because it is new.
TypeScript from the database schema to the browser. A column rename breaks the build instead of breaking a page at 2am.
Constraints, transactions and row-level security in the database — so a bug in a screen cannot hand one customer another customer's data.
Server-rendered pages arrive already drawn. Speed is not a polish step; a page that takes four seconds is one most people never scroll.
Every change runs through type checks, tests and a preview deploy before it reaches production. Releases stop being events.
The code behind these four claims
Press any of the four and you get the code that actually does it — copied out of this repository, file and line numbers included. Each one starts with a plain sentence saying what you are looking at, so you do not have to read the code to check the claim.
The four claims above — press one:
One description of the row, used by the query that reads it, the server action that writes it and the form that edits it. Rename a column and every place that has to change is listed before the code runs at all — which is the difference between a build failing and a page failing.
export type Profile = { id: string; role: Role; email: string; full_name: string | null; company: string | null; phone: string | null; locale: Locale; /** Panel rendering only — never a slot calculation. See lib/time/zones.ts. */ display_timezone: string | null;};Proof
A column rename, left half-finished, pushed at the four gates every change to this site walks through. Watch it stop at the first one — then finish it properly and push again.
mazarix/site · rename-member-idrecorded runStories of an ordinary day
None of them is about us. Each follows one person through an ordinary day and ends on a question about your company.
Try it now
میخواهماینPDFرابازکنم.
«PDF» stayed where it was said. That is the part everything else gets wrong.
The dictation engine behind our macOS app, running on this site. Speak Persian, read it back. A minute at a time; it stops when you stop.
Dictation is for members. Signing in brings you straight back here.
What changes
Stock, orders and revenue agree across every screen, because they come from one system rather than three spreadsheets.
The reports, the syncing, the reminders — done before anyone opens a laptop.
Customers and staff get an answer from the real catalogue or the real policy, at any hour.
Every order and movement is history you can query, so next season is a decision instead of a guess.
Writing
Engineering notes on testing, delivery and the operational systems a business grows into — the failures, the mechanisms, and what each one costs.
12 min read
Taking the order is the part that works. Everything after it — stock that stops agreeing, a hundred orders each needing a different action, returns, receipts, the question of what actually sold this year — is where a shop either has a system behind it or does not.
Read the article9 min read
A feature can be finished for a week and still not be in anyone's hands. What sits in that gap is usually a person, a set of steps they remember, and an evening nobody wanted to spend. This is what a pipeline replaces, stage by stage.
Read the article13 min read
An application that runs in a demo and an application that holds up under real users are two different things. This is the gap between them: the families of failure that live in it, and which layer of testing catches which.
Read the articleAutomation examples
Follow one customer message through five kinds of business: a shop, a clinic, trade and accounting, a factory and a warehouse. Each scene shows how the system reads the message and what it gets done without anyone stepping in.
Everything answerable from stock and the price list
| No. | Customer | Amount | Status |
|---|---|---|---|
| 1044 | Nicole · Marietta | $178 | Paid |
| 1043 | Sarah Mitchell | $95 | Paid |
| 1042 | Ridgeline Supply | $3,100 | Shipped |
| 1041 | Maria Alvarez | $840 | Paid |
Transparency
The system showing you this page was built the same way we build for you. The figures below were read from its own code and database just now; they are not a mock-up.
Last commit on main: 159c107
Straight answers
A focused automation is two to four weeks. A full operational system is usually three to six months, delivered in two-week increments you can use as they land — you are not waiting until the end to see it.
It depends on scope, and we will not pretend otherwise. After the first stage you get a written scope with a fixed estimate, before any build work starts. If the work is not worth doing, we say so then.
You own the running software, the data and the infrastructure it sits on, with full administrative access. Source code transfer is a separate arrangement — ask and we will price it.
Before any AI work begins we put in writing which data leaves your organisation and where it goes. Your data is never used to train a model and never appears in another client's project. Where sensitivity demands it, running the model on internal infrastructure is assessed and implemented if feasible.
Usually. Anything with an API, a database or even a scheduled file export can be connected. Where a system is genuinely closed, we will tell you before you spend anything.
You get an admin panel for the things that change often. Beyond that, new features are a separate piece of work with their own estimate — never an open-ended retainer you forgot you were paying.
Next step
A thirty-minute conversation about how your work moves today and where software would actually help. No slides, no obligation — and if the answer is that you do not need us, we will tell you.