Services
Interkey is a software company in Riyadh that has been building custom enterprise applications since 1999: for operators, government entities and industrial businesses that need software fitted to how they actually work.
Orientation
The whole page in one table, before the detail.
| Engagement models | Project delivery, dedicated team, or augmenting an existing in-house team |
|---|---|
| Disciplines | Frontend, backend, microservices, database administration, data engineering, DevOps |
| Team location | Riyadh, working the Sunday to Thursday week |
| Languages | Arabic and English, in documentation and in the room |
| Typical duration | From a scoped several-week build to a multi-year platform engagement |
| Handover | Source, documentation and deployment pipeline transfer to the client |
| Commercial model | Quote only: scoped per engagement |
The reality
Most organisations in the Kingdom do not need software written from nothing. They need a system that already exists to do something it was never designed for: serve a mobile app it predates, integrate with a government platform that launched last year, or survive a load it was never sized for.
That is most of what Interkey builds. It has been doing it since 1999: originally as IKeyData, when it worked as a data partner to Tadawul, the Saudi stock exchange. That is an unusually early date for a technology company in this market, and it means the systems being modernised now are often ones the team has watched through more than one generation.
The practical difference a local team makes is less about cost than about the working week. A supplier operating Monday to Friday is unavailable on Sunday, which is a working day here, and unavailable during the two days that matter most for a Thursday deployment. Requirements gathering in Arabic with the people who actually use the system, rather than through a translation layer, tends to surface the constraints that would otherwise appear during acceptance testing.
Disciplines
The largest share of the work. APIs, service layers and the integration between systems that were never designed to talk to each other. In this market that commonly means connecting something long-lived and internal to something new and external, in a way that does not require either to be rewritten.
Customer-facing portals and internal tools, built to work in Arabic and English with proper right-to-left support rather than a mirrored afterthought. RTL done badly is immediately obvious to an Arabic-speaking user and is one of the more common failures in software procured from outside the region.
Database administration, data modelling, pipelines and the migrations that move an organisation off a platform it has outgrown. Interkey works across relational and NoSQL platforms such as Couchbase, and the choice between them is a design decision rather than a default.
CI/CD pipelines, containerisation and Kubernetes, and the observability that tells you whether what you deployed is actually healthy. Software that cannot be deployed reliably is not finished, whatever the feature list says.
Engagement
Engagements take one of three shapes.
The outcome is defined and Interkey is accountable for it.
Engineers work as an extension of the client's organisation over a longer period.
Specific skills, a database specialist, a DevOps engineer, join an existing in-house team that is otherwise capable.
Choosing well
Which one fits depends less on the technology than on where the domain knowledge sits. If the client's team understands the problem deeply and lacks capacity, augmentation works. If the problem is understood but nobody has time to own it, project delivery works. The failure case is a scoped fixed-price project for a problem nobody has defined yet, and it is worth saying so before starting rather than discovering it at acceptance.
Handover is part of the deliverable: source, documentation and the deployment pipeline transfer to the client. Software that only its original authors can deploy is a liability being handed over as an asset.
Integration
Most serious projects in the Kingdom hit one point: connecting to a platform or system you do not control. It might be a government system with specific integration requirements, a fifteen-year-old ERP with no documented interfaces, or a banking system that cannot tolerate any downtime.
The work here is less about writing code than about understanding the constraints before committing to a timeline: what the other system actually allows, who has authority to change it, and how long approvals take. Scoping a project without answering these questions is the most common reason software projects run late in this market, and it has nothing to do with the technology.
That is why projects usually start with a short, paid discovery phase: examine the existing systems, establish what is actually possible, then estimate delivery on a realistic basis. That phase sometimes ends with a recommendation not to proceed with the project as proposed, and that is a useful outcome that saves a budget.
Cloud & containers
A growing share of these projects does not end at writing the application; it ends at running it on a container platform: building container images, designing and operating Kubernetes clusters, and the CI/CD pipelines that make deployment routine rather than an event. When systems require data and workloads to stay inside the Kingdom, that usually means a self-managed platform on local infrastructure, engineering work that needs someone to own it for years, not just a purchase decision. After go-live comes monitoring: no serious system is complete without real visibility into its health, with dashboards and alerts the team trusts rather than noise everyone learns to ignore.
Choosing a vendor
These criteria are not self-praise, they are a checklist that works for any vendor you are comparing. Ask for the answers in writing, and compare.
Sectors
Government and semi-government entities, telecommunications operators, energy and industrial businesses, and e-commerce and logistics. Interkey delivers into environments of that kind, which means the compliance, procurement and security review processes these projects have to pass are familiar rather than a surprise late in delivery.
Where a build needs messaging, it connects to Interkey Digital Connect for SMS, OTP and WhatsApp rather than requiring a separate supplier and a separate integration.
When this is the wrong fit: a requirement that a configured product already meets. Buying and configuring is cheaper than building on the day, and it stays cheaper for the whole life of the thing, because somebody else carries the maintenance. Building is the right answer when the process is the differentiator, or when no product fits without changing how the business works.
Buyer questions
Direct answers to the questions that come up in real evaluations. Anything missing, ask us at the bottom of the page.
Mostly existing ones. The common engagement is extending, integrating or modernising a system that already runs the business, usually while it stays in service. Complete rewrites are rarer and are normally the wrong answer.
Yes, in Riyadh, working the Sunday to Thursday week. That matters more than it sounds: a supplier on a Monday to Friday calendar is unavailable on the first day of the Saudi working week and during a Thursday deployment window.
Yes, in requirements sessions, documentation and the delivered interface. Arabic right-to-left support is built in rather than mirrored on at the end, which is a common failure in software procured from outside the region.
Yes. Source, documentation and the deployment pipeline transfer to you. Software only its authors can deploy is a liability, not an asset.
Per engagement, on a quote basis, because the three delivery shapes price very differently. The scoping conversation is about which shape fits the problem, and that determines the commercial model rather than the other way round.
From the insights library
For the platforms these builds increasingly land on: how visibility is designed in rather than added later.
Migration guideWhen a build includes moving off the old data platform, this is the sequence that keeps it from becoming an outage.
Procurement guideFor applications that send SMS or OTP: the registration step that decides whether messages deliver at all.
PracticeConnecting what you build to the systems the organisation already runs, with an owner per interface.
PracticeGoverning the interfaces once they exist: who may call them, at what rate, in which version.
Sector guideArabic-first delivery, in-Kingdom end to end, and operation after handover.
Explore related solutions
Next step
Describe the system in the words you would use to a colleague — what it should do, what it must connect to, what worries you. Scoping is our job, not yours.
Riyadh team on the Saudi working week
Requirements, documentation and delivery in Arabic and English
You own the code
Source, documentation and pipeline transfer at handover
Working with Saudi enterprises since 1999
Originally as IKeyData, data partner to Tadawul
A Saudi contracting entity
Registered in Riyadh, CR 1010156897
Or directly
+966-11-2180999 info@interkey.com.saTawuniya Towers, North Tower, 7th Floor, King Fahad Highway, Olaya, P.O. Box 56835, Riyadh 11564, Saudi Arabia