About us
We live with what we build
CoreInnovation is a software company in Jordan. We design and build web platforms, mobile apps and AI products — and we own and operate three of our own, with subscribers paying for them every month. The second part is why the first part is any good: when you carry your own product past launch, you stop shipping decisions you would not want to maintain.
The name is younger than the company
We started as CoreTechX. When we filed for commercial registration the name was rejected, so in June 2026 the company became CoreInnovation — and نواة الابتكار للبرمجيات on the registration itself.
The Arabic is not a transliteration of the English, and the English is not a translation of the Arabic. Nawat al-ibtikar means the core, the nucleus, of innovation. Both names say the same thing, which is rarer in a bilingual brand than it sounds — and it set the standard we hold the products to.
How we work
Four rules that decide what we build and what we refuse to.
A product, not a project
A project ends at handover. A product has a second year, and a third, and someone other than its author reading its logs at two in the morning. We build for that from the first commit: migrations safe to run twice, errors that say what to do about them, and an admin screen for whatever will inevitably need changing after launch. It is slower in month one and it is the only thing that is cheaper in year two.
Arabic is a design language, not a translation layer
RTL changes layout, not only direction. Numbers still run left to right inside a right-to-left sentence. Forms mirror, but a row of OTP boxes does not — fill those right to left and you get a reversed, invalid code. A typeface that is comfortable in Latin can be unreadable at 14px in Arabic. We design both directions at the same time, because retrofitting one onto the other always shows.
AI only where it earns its place
A model that sounds confident and is wrong is worse than no feature. So Nabih Edu answers only from the Jordanian Ministry of Education textbooks and cites the lesson and page range with every answer, because a teacher cannot fact-check a fluent invention. And Nabih asks a short question when a detail is missing instead of filling the gap itself.
End to end, including the boring end
Design, build, deploy, and then keep it running. Our own products sit on our own servers, which means we get the 3am page, the migration that locked a table, and the certificate that expired on a Friday. That is the part of software most vendors never experience on the systems they sell.
Seven products, and a line between them
Four are systems we sell and install for an organisation of your own: point of sale and e-invoicing, queue management, school administration, charity administration. Three are ours — we built them, we run them, and their users are drivers, lawyers, doctors and teachers, not buyers. We keep the two groups visibly apart on this site because they are two different conversations, and because the second group is the honest answer to “can you actually build something like this for us?”
Systems you can run tomorrow
What we build with
Next.js and React on the web, Flutter for mobile, Node and MySQL behind them, and Groq-hosted models where a product needs one. We pick boring, well-documented tools on purpose: the interesting part of a product should be the product.
Tell us what you are trying to fix
A first conversation costs nothing and usually ends with a straight answer about whether we are the right people for it.