ASAL Cloud is brand-new, so we won't show you customer logos or migration counts we haven't earned yet. Instead, here's the real thing: the engineering pedigree behind us, and exactly how we'd run your engagement — step by step.
Honest by design. Zero signed customers so far — the engagement stories below are representative blueprints of how we work, not delivered results with metrics.
The foundation
25 years of engineering, one new AWS practice
Two decades engineering for the world's technology leaders — as ASAL Technologies
These are R&D engineering clients of ASAL Technologies — not AWS channel partners, and not references for ASAL Cloud. They're the bench now standing behind this practice.
The real proof
Our track record isn't AWS migrations yet — it's 25 years of engineering
ASAL Cloud launched in 2026 with no signed AWS customers. What it inherits is an established R&D engineering company: ASAL Technologies has been trusted to build for global technology leaders since 2000. That's the proof that actually exists today.
2000Founded — over two decades of continuous software delivery
450+Engineers across Palestine, Jordan & the UAE
8Global tech leaders trusted ASAL to engineer their R&D
3Countries of delivery — Arabic-first across MENA
Trusted to engineer for — two decades of R&D
Microsoft
Intel
Cisco
Qualcomm
Synopsys
Western Digital
Cadence
Wix
To be clear: these are engineering clients of ASAL Technologies — companies we've been trusted to build R&D for. They are not AWS partners, references for ASAL Cloud, or endorsements of this practice.
How we'd work
Engagement blueprints — not case studies
Since we have no delivered projects to point to, here's the honest alternative: representative engagements, each laid out as Challenge → Approach & architecture → What you'd get. These describe how we'd run the work and what we'd build — they are illustrative, not records of past results or guaranteed outcomes.
Scenario · GenAI
Knowledge-base assistant
Representative blueprint
A support team drowning in a 4,000-page document library
CHA
Challenge
Agents spend hours hunting across PDFs and wikis for answers, and replies are inconsistent. The team wants AI help but can't risk a black-box tool inventing facts.
APP
Approach & architecture
We'd build a RAG assistant on Amazon Bedrock: ingest documents to S3, embed and index them in a vector store, and ground every answer in retrieved passages with citations — in a fixed 60–90 day PoC, structured to pursue AWS PoC funding where eligible.
OUT
What you'd get
A working demo your team can query, an honest accuracy read, a cost-per-query model, and a clear go / no-go decision — a prototype, not a slide deck.
Illustrative architecture · RAG on Bedrock
Scenario · Modernize
Off Microsoft licensing
Representative blueprint
A .NET app on Azure with a SQL Server bill that keeps climbing
CHA
Challenge
A business-critical .NET / SQL Server workload runs on Azure, with Windows and SQL licensing costs rising every renewal. The team wants out, but can't afford a risky big-bang rewrite.
APP
Approach & architecture
We'd start with a no-cost Modernization Viability Assessment, then move in waves: SQL Server → Amazon Aurora, Windows → Linux, and .NET re-platformed onto AWS-managed compute — with rehearsals and rollback plans, structured to pursue AWS modernization funding where eligible.
OUT
What you'd get
A licensing-light target architecture, a phased migration runbook, and a cost model showing the recurring spend you'd remove — plus the funding paths your project may qualify for.
Illustrative path · Azure → AWS
Scenario · Foundation
Secure landing zone
Representative blueprint
A regulated scale-up about to put real workloads on a single AWS account
CHA
Challenge
Everything lives in one AWS account with shared credentials and no guardrails. Auditors are asking about data residency and separation of duties before the next funding round.
APP
Approach & architecture
We'd stand up a multi-account landing zone on AWS Control Tower with the Landing Zone Accelerator: separate prod / non-prod / security accounts, centralized logging, SSO, and guardrail policies — often AWS-funded for net-new estates where eligible.
OUT
What you'd get
A compliance-ready account structure you own, baseline guardrails enforced automatically, and an audit-friendly foundation to grow on — handed over with documentation, not lock-in.
Illustrative layout · Control Tower
No blueprints in this category yet — try another filter.
Our methodology
The same disciplined path on every engagement
We can't show you finished AWS projects yet — but we can show you exactly how we'd run one. This is the method behind every blueprint above, from the funded first step to a foundation you operate yourself.
1
Step 1 · usually funded
Assess
A low-cost, often AWS-funded readiness review of your workloads — plus a first read on which AWS programs your project may qualify for. No commitment to go further.
Readiness reviewFunding eligibility
2
Step 2 · plan
Architect & cost-model
A target architecture, a migration or build plan in waves, a transparent cost model, and the specific AWS funding we'd pursue on your behalf — written down before any build starts.
Target architectureCost modelFunding plan
3
Step 3 · build
Deliver in waves
Senior architects build and migrate incrementally — with rehearsals, rollback plans, and a working result at each milestone. You see a prototype or a live cutover, never a status slide.
Rehearsed cutoversRollback plansSenior-led
4
Step 4 · operate & hand over
Run, optimize & hand over
Managed operations, FinOps guardrails, and ongoing Well-Architected check-ins — with documentation and access so you own the environment, not a dependency on us.
FinOps guardrailsWell-ArchitectedYou own it
Be one of the first stories we're proud to publish.