Own the whole stack
Data model, services, interface and deployment are designed together, by the same people.
About
An AI-first product studio
ColorsX74 builds its own software products and takes on selected client work. Products lead; client projects prove the engineering behind them.
Why a product studio
An agency hands over a deliverable and moves on. We build products we have to live with, so the data model, the deployment and the support load are our problem — not a future client’s.
That changes how we design. Fewer clever abstractions, more systems that hold up under daily use.
How we build
Engineering principles
AI where it does work
AI earns its place when it removes setup, data entry or analysis — not when it decorates a screen.
Bilingual from the first commit
Arabic and English are both first-class, right-to-left included. Translation is not a phase at the end.
Ship small, run it, then extend
A narrow system in production beats a broad one in staging. Modules arrive once the core has earned them.
How we work
From scope to running system
Four steps, in this order, on every project.
-
Map the real workflow
Before any schema, we walk the process as it actually happens — including the exceptions people work around.
In practice
Business systems break on the exceptions, not the happy path — the contract that gets amended, the rental returned early, the sale invoiced before the purchase lands. Those cases decide the data model, so they are mapped before anything is designed.
-
Build the core first
The smallest complete system that can run real work, with a data model designed to outlive it.
In practice
The trading engine is the clearest case: one codebase runs backtest, paper and live, so a strategy is never re-implemented for the mode it is finally traded in.
-
Run it, then fix what reality finds
We deploy early and use the system ourselves. Production tells the truth faster than any review meeting.
In practice
We are the first user. The ERP is in production and the trading engine was built to run our own trading, so the first bug report is ours, not a client’s.
-
Extend module by module
A new module ships once the core has earned it — never as a promise made at the start.
In practice
The ERP grew exactly that way — accounting, sales, purchase, contracts, rental and a POS kiosk on one core — and Commerce reaches it through an optional connector module, not a dependency welded into either side.
In the code
What our repositories have in common
Five habits that do not change between an ERP module and a client’s marketing site.
Two languages, one build
Arabic and English come out of the same source. The Arabic side mirrors properly — logical layout, direction-aware icons, a typeface picked for Arabic instead of borrowed from the Latin one. This page is the sample: switch it and nothing falls over.
Static first
Marketing sites ship as pre-built pages with near-zero client-side JavaScript. Nothing is assembled while the visitor waits, so there is nothing to be slow and nothing to patch at three in the morning.
Fonts we host, visitors we do not track
Typefaces are served from the same origin as the page. No analytics, no tag manager, no third-party script. Somebody opening one of our sites is not announced to anyone else.
One deployment path for everything
Products and client sites go out the same way, with the same certificate handling and the same health checks. A new project is not a new operations problem — it is one more thing that deploys like the rest.
Documentation ships with the product
The ERP has a public documentation site, open to anyone, rather than a file handed over at the end of a project. A system nobody can read is a system nobody else can run.
The stack
What we build with
.NET and PostgreSQL under our platforms; Angular and Astro on the front. Message queues, single sign-on and exchange APIs wherever one system has to talk to another.
- .NET
- PostgreSQL
- RabbitMQ
- Redis
- Keycloak SSO
- Angular
- Binance API
- Binance testnet
- Astro
Next step
Want to see it running?
You get the running system, not a slide deck.