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.
- Data model
- Services
- Interface
- Deployment
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.
- A finished system
- Agency
- Hand over then moves on
- Studio
- Running it
- Supporting it
- Extending it
- Products
- ColorsX74 ERPColorsX74 CommerceCX74 Trading EngineCity Brain
- Selected work
- Nubes Real EstateSold Out Events
- Proposal
- Madarek
- Location
- United Arab Emirates
Engineering principles
-
Own the whole stack
Data model, services, interface and deployment are designed together, by the same people.
-
AI where it does work
AI earns its place when it removes setup, data entry or analysis — not when it decorates a screen.
- EN AR
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.
From scope to running system
-
Map the real workflow
Before any schema, we walk the process as it actually happens — including the exceptions people work around.
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.
The trading engine is the clearest case: backtest, paper and live are three modes of one codebase, so a strategy is never rewritten to move from one mode to the next.
-
Run it, then fix what reality finds
We deploy early and use the system ourselves. Production tells the truth faster than any review meeting.
We are the first user. The ERP is in production, and we run Commerce in preview and the trading engine in paper mode ourselves, 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.
The ERP grew exactly that way — accounting, sales, purchase, contracts, rental and a POS kiosk on one core — and Commerce is built to reach it through a connector module, planned as an option rather than a dependency welded into either side.
What our repositories have in common
Five habits that do not change between an ERP module and a client’s marketing site.
- src/i18n/ui.ts
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.
- dist/
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.
- src/styles/fonts.css
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.
- scripts/*-gate.mjs
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.
- documents.erp.colorsx74.com
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.
What we build with
.NET, Python and PostgreSQL under our platforms; Angular, React and Astro on the front. Message queues, single sign-on and exchange APIs wherever one system has to talk to another.
-
Interface
- Angular
- React
- Astro
-
Platform
- .NET
- Python
-
Data
- PostgreSQL
- Redis
-
Integration
- RabbitMQ
- Keycloak SSO
Want to see it running?
You get the running system, not a slide deck.