Nawa
عربيEN
Start a project

Software engineering · Hebron, Palestine

An engineering partner that owns the work — from the first question to production.

Nawa designs, builds and runs custom software, cloud infrastructure and automation. We take responsibility for the whole path: understanding the problem, choosing the architecture, delivering it, and handing it over properly.

Start a projectView our work
Custom softwareCloud & infrastructureAutomationModernization & integration

01How we work

One responsibility, from understanding to handover.

We don’t deliver disconnected parts for someone else to assemble. The same team understands the problem, designs the solution, builds it, runs it in production and hands it over documented.

  1. 01

    Understand · Discovery

    We start with the problem, not the solution: current workflows, constraints, existing systems, and what success actually means.

    Output: problem statement · constraints · clear scope

  2. 02

    Architecture · Solution design

    We choose the architecture and record decisions and their alternatives before writing code, so the system stays maintainable and extensible.

    Output: architecture diagram · decision record · delivery plan

  3. 03

    Build · Test

    We build in reviewable increments, with code review, verification proportional to risk, and an automated delivery pipeline from day one.

    Output: reviewed releases · CI/CD · regular reviews

  4. production
    04

    Deploy · Handover

    We deploy to production and hand the system over documented and understood, with clear ownership of operations.

    Output: production deployment · documentation · structured handover

02Services

Four capabilities. One engineering system.

A business rarely needs just one. Software runs on infrastructure, integrates with existing systems, and automates work that used to be manual — so we design them together.

Explore services
  • 01

    Custom software development

    Web platforms, mobile apps and internal systems built around how your organization actually works — not around a template.

    Web platformsiOS & Android appsAdmin systemsAPIs
  • 02

    Cloud & infrastructure

    Secure, scalable cloud infrastructure with understandable cost, automated delivery and clear monitoring.

    Cloud architectureContainersCI/CDMonitoring & alerting
  • 03

    Automation

    Automating repetitive work and data flows, with a human review step wherever a decision is needed.

    WorkflowsData pipelinesAI-assisted processing
  • 04

    Software modernization & integration

    We modernize existing systems or build a modern layer around them — without replacing what works for no reason.

    ERP integrationAPI layersIncremental modernization

03Selected work

Engineering is visible in the work itself.

All work
Rihab marketplace storefront on desktop: search, categories, shops and offers (Arabic UI)
rihab.appStorefront — shops, malls and categories in one place.
Nawa Product

Rihab

A Palestinian digital marketplace connecting customers with Palestinian shops and vendors. We built the whole system: shopping, merchant operations, order orchestration through delivery, and a Facebook product importer.

  • Marketplace & mobile experiences
  • Merchant operations, offers, agreements
  • Order-to-fulfillment orchestration
  • Facebook content → catalog importer
Read the case study
Client Work

Magic Car

A B2B trader platform built around an existing ERP. The ERP stays authoritative; we built a modern layer around it for traders and administrators.

Flutter · Web · iOS · Android

S3 → Lambda → CloudFront

Read the case study
Magic Car catalog: products with price, availability and item number (Arabic UI)
01Catalog
Trader cart with quantities, line notes and an estimated total
02Cart — estimated total, confirmed by the ERP
Trader orders with accepted, rejected and in-review states
03Orders and their states

04Engineering note

Integration, not unnecessary replacement.

At Magic Car the ERP remained the source of truth for products, prices and accounts. Our integration layer keeps a last-known-good catalog so the app stays available, and re-validates price and availability against the ERP when each order is reviewed — cache for reads, the live ERP for commercial decisions.

Simplified architecture · Magic Carexternal diagram · v1
Existing business systemNawa integration layerTrader experiencesynccatalog readsplace orderlive validationadmin actionsERPAuthoritative for products,prices, accounts and ordersRemains in placeCatalog syncLast-known-goodcatalog cacheLive validationafter admin reviewAdmin · campaigns · accountsOperational workflows around the ERPFlutter clientWeb · iOS · AndroidCatalog · cart · ordersAccount workflowsS3LambdaCloudFrontMedia pipeline
Existing business system
ERP
Authoritative for products, prices, accounts
live validation ↑ · sync ↓
Nawa integration layer
Last-known-good catalog
Admin review + live validation
catalog reads · place order
Trader experience
Flutter client
Web · iOS · Android

media: S3 → Lambda → CloudFront

Simplified external view. The full architecture is in the case study.

Read the case study

05Why Nawa

We take responsibility for the outcome, not just the tasks.

01
Responsibility for delivery
We stay accountable until the system runs in production and is clearly handed over — not until the contract period ends.
02
Architecture before code
Material technical decisions are recorded with their reasons and alternatives, so you — and whoever comes after us — can understand them.
03
Secure and maintainable by default
Security, appropriate verification and documentation are part of the work, not an add-on at the end.
04
Honest scope, clear agreements
We say what we can and can’t do, and we take on projects we can deliver with integrity.

Have a system to build, fix, or connect?

Tell us about the problem. We’ll come back with good questions before any quote.

Start a projectMessage us on WhatsApp

[email protected] · +972 599 914 084