Working with the public sector

Government procurement asks specific questions. Here are our answers, so you can qualify us before the first meeting.

  1. Two government systems in production

    Nationwide traffic enforcement in Saudi Arabia and a land and tax registry in Palestine, both delivered with full handover.

  2. Deploys where your data lives

    On-premise, government cloud or sovereign region. Nothing leaves the jurisdiction unless the contract allows it.

  3. Engineers answer your RFP

    The people who write the proposal build the system and stay through handover. No handoff to a delivery team you have never met.

Reference deployments

Both are live today. Details, references and site visits are available under NDA.

Tahakom · Saudi Arabia · 2018–present

Phone and seat‑belt violation detection

Computer vision that flags phone use and unbuckled belts from roadside cameras, in production across Saudi Arabia since 2018.

  • Detection models for phone use and seat-belt state
  • Frame ingestion, tracking and evidence assembly
  • Human-review tooling and audit trail

In production, nationwide

Security and compliance controls

What evaluation committees usually ask, how we implement it, and the evidence you receive.

ControlHow we implement itEvidence you receive
Data residencyOn-premise or in the region and provider you name. No external calls from production without written approval.Network diagram and data-flow register
Access controlRole-based access, MFA for administrators, least-privilege infrastructure.Access matrix and admin list
Audit trailEvery change attributed and timestamped. Enforcement decisions carry frame, model version and confidence.Immutable log export on request
Security testingIndependent penetration test before go-live. Findings fixed within the contract.Test report and remediation record
Backup and recoveryRecovery objectives agreed in writing and rehearsed before launch.Disaster-recovery runbook and drill record
Ownership and escrowSource code in a repository you own from day one. Infrastructure as code.Signed handover checklist
Accessibility and ArabicWCAG 2.1 AA target, right-to-left layout designed first, Hijri and Gregorian dates.Accessibility audit and bilingual screens
SupportResponse and resolution times by severity, named engineer, monthly report.Support agreement and SLA report

Ways to engage us

Three routes that fit most public procurement rules.

  1. Respond to your tender

    Send the RFP or RFI. You receive a compliant response with fixed-scope pricing where requirements are stable, and time-and-materials with a cap where they are not.

    Typical turnaround: 10 working days

  2. Paid discovery first

    A fixed-price, two to four week discovery produces the scope, architecture and estimate you can attach to a tender or a direct award.

    Fixed price, deliverables owned by you

  3. Through a local partner

    Where rules require a registered local contractor, we deliver as the named technical subcontractor and remain the accountable engineering party.

    Partners in Saudi Arabia and Palestine

A typical programme

A six-month citizen-facing system, from first workshop to independent operation. Larger programmes repeat the build and verify phases.

  1. DiscoveryWeeks 1–4

    Process mapping, data assessment, architecture, written estimate.

  2. Build in incrementsWeeks 5–18

    Working software every two weeks on your infrastructure. Migration rehearsals.

  3. VerifyWeeks 17–21

    Penetration test, load test, user acceptance with your staff.

  4. Go-live and hypercareWeeks 22–24

    Cut-over, on-site presence, daily reporting.

  5. Handover and supportWeek 25 on

    Training, documentation, signed checklist, support agreement.

What we need from you

Projects that go well share a few things on the client side.

  1. A named sponsor with authority to decide.
  2. Access to the people who run the process today.
  3. A sample of real data, under NDA, during discovery.
  4. A decision on hosting and data residency before build starts.
  5. Staff time for acceptance testing and training.

Documents on request

  • Company registration and trade licence
  • Company profile (PDF)
  • Sample support agreement and SLA
  • Security questionnaire responses
  • Reference contacts, under NDA

Company profile

Common questions

Can you work within our infrastructure and security policies?

Yes. Our largest deployment runs entirely inside the client's own data centre with no external connectivity. We adapt tooling and process to your policies.

Do you subcontract?

Core engineering is in-house. Where a tender needs a local partner or a specialist, we say so in the proposal and remain the single accountable party.

What happens after go-live?

A support agreement with defined SLAs, or a full handover to your team with training. Many clients choose both for the first year.

How do you price?

Discovery is fixed-price. Build is fixed-scope where requirements are stable, and time-and-materials with a cap where they are not. Either way you receive a written estimate before commitment.

Can your engineers work on site?

Yes. Discovery workshops, acceptance testing, go-live and training are normally on site. Build work runs from our engineering centre with your stakeholders reviewing working software every two weeks.

Do you hold security certifications?

Our delivery process follows ISO 27001 controls and we support your auditors with evidence at every stage. Ask us for the current status of formal certification when you send the RFP.

What happens to our data after the project?

It stays with you. We hold no copies after handover, and any data used during discovery is deleted under the NDA terms.

Planning a digital transformation, an AI pilot or a citizen-facing service?

Send us the brief or the tender documents. You will hear back from an engineer, not a salesperson, within two working days.