Skip to content
Syed Omar Ibn FerojSyed Omar Ibn Feroj
Operating · Dhaka → Global

Engineeringenterprise infrastructurefor the intelligent digital era.

A multi-disciplinary executive operating at the intersection of telecommunications infrastructure, enterprise software, cloud systems and AI-integrated operations. Architect of resilient platforms for telecom operators, regulated industries and large-scale enterprises.

Enterprise Technology Leadership
Cloud-Native Infrastructure & DevOps
Cybersecurity & Infrastructure Resilience
Operational Intelligence & AI Integration
Strategic Digital Transformation
International Enterprise Collaboration
Infrastructure · Operating
Syed Omar Ibn Feroj
PrincipalSyed Omar Ibn FerojRupam · Omar Bhai
Executive Profile · 01
01Executive Overview

A multi-disciplinary executive operating at the intersection of infrastructure, software and capital.

Syed Omar Ibn Feroj — known professionally as Rupam — leads a portfolio of operating entities focused on telecommunications platforms, enterprise software and AI-integrated operations. The work is unapologetically infrastructure-first: long-horizon, regulated, mission-critical.

Global Operating Posture

Engagements span operators, enterprises and regulated environments — engineered for cross-jurisdictional deployment from day one.

Position

Work is scoped for more than one jurisdiction from the outset, with operator engagements running across South and Southeast Asia. Data residency and local regulation are design inputs, not launch-week discoveries.

Pillar · 01

Engineering Depth

Hands-on across language runtimes, distributed systems, kernel and network stacks — leadership grounded in operating reality.

Position

Leadership that still reads the diff: language runtimes and distributed services through to kernel, storage and network layers. Decisions get made close to the evidence rather than from a summary two layers removed.

Pillar · 02

Operational Intelligence

AI-integrated workflows, autonomous runbooks and observability fabrics that turn infrastructure into a reasoning surface.

Position

Observability first, then reasoning placed on top of it — retrieval over an estate's own telemetry and documentation. Agentic runbooks carry the repetitive half of an incident under scoped permissions and an audit trail.

Pillar · 03

Infrastructure-First

Data centers, networks and platforms designed for long-horizon continuity, regulatory compliance and operator-grade reliability.

Position

The bias runs toward assets that compound: data centres, networks and platforms planned in decades rather than quarters. Continuity, compliance and operator-grade reliability outrank release velocity when the two conflict.

Pillar · 04
Ecosystem · 02
02Company Ecosystem

Two operating entities. One coherent thesis.

A coordinated portfolio architected for telecommunications operators, enterprises and regulated industries — with shared platform leverage and disciplined engineering practice.

i-VAS Solution logo

i-VAS Solution

Operational Intelligence for Telecom & Enterprise

Entity · 01

A specialised value-added services and infrastructure operator delivering platforms for telecommunications carriers, enterprises and regulated environments. Covers VAS platforms, carrier-grade middleware, AI-driven service orchestration and integrated operational systems.

Mandate

i-VAS works on the operator side of the boundary: services that run inside a carrier's environment and are judged by carrier standards — signalling correctness, provisioning and rating paths that reconcile, and change windows measured in minutes rather than sprints. The platform work runs from messaging and voice service logic through to the orchestration layer that turns a commercial product into something a network can actually provision, meter and bill. Enterprise middleware and operational analytics carry the same discipline outward, giving businesses operator-grade delivery guarantees on channels they normally buy as best-effort.

Capability Pillars
  • Carrier-Grade VAS Platforms
  • Telecom Service Orchestration
  • AI-Integrated Operations
  • Enterprise Middleware
  • Operational Analytics
TelecomEnterpriseRegulated Industries
Engage on partnerships
FAR INTEL BANGLADESH logo

FAR INTEL BANGLADESH

Infrastructure, Automation, Intelligent Systems

Entity · 02

Engineering enterprise platforms, data systems and digital transformation programs across regulated and industrial sectors. Specialised in deployment, automation, intelligent operations and long-horizon infrastructure strategy.

Mandate

FAR INTEL takes the enterprise and infrastructure side: the platforms, cloud programmes and physical estate that regulated and industrial organisations run their operations on. Engagements usually begin where a modernisation programme meets an audit obligation — legacy systems that cannot simply be switched off, a security posture that has to be demonstrable rather than asserted, and data-centre capacity planned years ahead of the workload that will land on it. Work is structured as a programme rather than a project: architecture, deployment, hardening, and the operational handover that decides whether any of it survives its first year.

Capability Pillars
  • Enterprise Software Engineering
  • Cloud & DevOps Programs
  • Cybersecurity Architecture
  • Data Center Engineering
  • Industrial & Smart Operations
IndustrialPublic SectorHealthcareLogistics
Engage on partnerships
Numbers · 03
03Numbers That Matter

Scale, measured. Not asserted.

Figures computed directly from documented telecom engagements — counters move as the verified record grows.

0
Mobile Operators

Counted from the documented operator record — one entry per carrier, no duplicates across engagements.

0
Countries

Distinct markets in that record, spanning South Asia and Southeast Asia through North America and Oceania.

0+
Service Categories

Distinct VAS and platform services engaged across those operators — deduplicated, not summed per engagement.

0+
Years Experience
indicative

The one figure here that is stated rather than derived from the record.

Mobile Operators · 04
04Mobile Operators

Operators served, by country.

Named carrier engagements grouped by market. Each card expands into the services, technologies and domains delivered — with an honest experience tier.

Bangladesh5 operators
India11 operators
Thailand2 operators
Malaysia1 operator
Singapore1 operator
Myanmar3 operators
Philippines2 operators
Canada2 operators
Australia1 operator
Other Fields · 05
05Other Fields I Worked

Beyond telecom, across other sectors.

Higher education, government, pharmaceutical, insurance and enterprise organisations served outside the mobile-operator practice.

Technology Procurement Mandate

For universities and public institutions, engagements extend beyond software delivery to end-to-end technology procurement — carrying an institution from requirement definition through to a commissioned, supported system.

  1. 01
    Solution Design

    Requirement analysis and target architecture.

  2. 02
    Technical Specification

    Tender-grade specifications and compliance criteria.

  3. 03
    Vendor Evaluation

    Structured assessment against defined criteria.

  4. 04
    Procurement Management

    Process governance through to award.

  5. 05
    Deployment

    Rollout, integration and commissioning.

  6. 06
    Post-Implementation Support

    Operational continuity after handover.

North South University

North South University

Education

United International University

United International University

Education

East West University

East West University

Education

Bangladesh Agricultural University

Bangladesh Agricultural University

Education

Civil Aviation Authority

Civil Aviation Authority

Government

Eskayef Pharmaceuticals Limited

Eskayef Pharmaceuticals Limited

Pharmaceutical

MetLife

MetLife

Insurance

Qlik

Qlik

Enterprise

Acsys International

Acsys International

Enterprise

CRATUS

CRATUS

Enterprise

FSM Global

FSM Global

Enterprise

Products & Services · 06
06Telecom Services

Products & services, categorized.

A comprehensive taxonomy of telecom services and platforms delivered — from messaging and voice to enterprise APIs, IoT and AI-integrated systems.

8 categories · 49 services

AI

The reasoning layer added on top — model integration, language services and automated workflows.

ai-integration

AI Integration

LLM and AI model deployment within systems

llm

LLM

Large language model services for natural language processing

workflow-automation

Workflow Automation

Automated business processes and intelligent workflows

agentic-systems

Agentic Systems

Autonomous agent systems for task automation

Cloud

The runtime beneath the platforms: containers, orchestration, monitoring and deployment that survives a node loss.

kubernetes

Kubernetes

Container orchestration and deployment platform

docker

Docker

Containerization technology for application packaging

devops

DevOps

Development and operations automation and practices

monitoring

Monitoring

System health, performance tracking and alerting

high-availability

High Availability

Resilient and fault-tolerant service deployment

Digital

Subscriber-facing content delivered over the operator's channel and, critically, its billing relationship.

music

Music

Music streaming and download services for mobile subscribers

video

Video

Video content delivery and streaming platform

games

Games

Mobile gaming services and platform for casual gaming

wap

WAP

Wireless application protocol for mobile web content

app-store

App Store

Application distribution and discovery platform

ott

OTT

Over-the-top video and entertainment streaming service

news

News

Real-time news delivery and content service

sports

Sports

Live sports content, scores, and updates service

prayer-time

Prayer Time

Prayer schedule and religious content service

horoscope

Horoscope

Daily horoscope and astrology content service

Enterprise

Carrier capability exposed to businesses — protocols, APIs and identity consumed by applications rather than subscribers.

smpp-svc

SMPP

Protocol for SMS transmission between applications and servers

cpaas

CPaaS

Communications platform as a service for enterprises

api-gateway

API Gateway

Access carrier services and resources via REST APIs

location-api

Location API

Query and track subscriber location data for services

ent-messaging

Enterprise Messaging

Business-grade messaging solutions for enterprises

digital-identity

Digital Identity

Identity verification and authentication service

Financial

Money movement over the mobile channel: wallets, top-ups, transfers and bill payment, with the reconciliation demands that follow.

mobile-money

Mobile Money

Digital wallet and payment service for mobile transactions

recharge

Recharge

Mobile credit top-up and prepaid balance service

bill-payment

Bill Payment

Pay utilities and services via mobile phone

wallet

Wallet

Digital money storage and transaction service

airtime-transfer

Airtime Transfer

Send mobile credit to other subscribers

IoT

Connectivity for devices instead of people — SIM provisioning, machine traffic and asset tracking.

iot

IoT

Machine-to-device connectivity and communication

esim

eSIM

Embedded SIM technology for IoT devices

m2m

M2M

Machine-to-machine communication and automation

fleet-tracking

Fleet Tracking

GPS tracking and monitoring for vehicles and assets

Messaging

Store-and-forward and session-based subscriber messaging — the SMSC and SMPP layer carriers monetise most directly.

sms-gateway

SMS Gateway

Transmit SMS to mobile subscribers via carrier networks

premium-sms

Premium SMS

High-value SMS services with premium content and revenue sharing

bulk-sms

Bulk SMS

Send large volumes of SMS messages efficiently at scale

a2p

A2P

Application-to-Person messaging for customer notifications and alerts

p2p

P2P

Person-to-Person messaging between mobile subscribers

flash-sms

Flash SMS

Immediate popup SMS that displays without storing in inbox

otp

OTP

One-time password delivery for authentication and security

ussd

USSD

Menu-based communication platform for interactive services

cell-broadcast

Cell Broadcast

Emergency and public warning messages to all devices in an area

Voice

Services on the call path: menus, tones, alerts and completion logic running against the switching layer.

ivr

IVR

Interactive voice systems for automated customer interactions

voice-portal

Voice Portal

Access information and services via phone menu systems

voicemail

Voicemail

Store and retrieve voice messages from callers

rbt

Ring Back Tone

Custom tone played to callers instead of default ringtone

mca

Missed Call Alert

Notification to subscriber when incoming call is missed

call-completion

Call Completion

Forward and complete calls through gateways and networks

Proficiency Matrix · 07
07Proficiency Matrix

Skills mapped to proficiency levels.

A structured view of technical depth — from platform architecture to emerging technologies — rated 1-5 with honest experience tiers. No inflated claims.

Capabilities

14

Categories

9

Average Depth

3.7

Billing & Charging

Rating, charging and revenue paths — where a service becomes billable, reconcilable and auditable.

Charging & Billing (OCS, PCRF)

Integration

Prepaid/postpaid, OCS, PCRF, charging gateways

3/5

Core Telecom

The network elements and signalling a service must interwork with to exist at all — SS7, SIP, Diameter, HLR/HSS and IMS.

Signaling Protocols (SS7, SIP, Diameter)

Direct

SS7, SIP, Diameter protocol stacks

4/5

Core Telecom Systems (HLR, HSS, IMS)

Integration

HLR, HSS, IMS platforms, integration experience

3/5

Digital Services

Content products delivered through the operator channel: music, video, games, OTT and app distribution.

Digital Content Platforms (Music, Video, Games)

Integration

OTT, music, video, games, app store

3/5

Emerging Tech

Newer surfaces being built against and tracked deliberately, rather than claimed as settled practice.

AI/ML Integration (LLMs, Automation)

Integration

LLM integration, workflow automation, agentic systems

3/5

Enterprise Architecture

The structure around the platforms: APIs and integration, container runtime, CI/CD and orchestration.

API Integration & Architecture

Direct

REST/SOAP APIs, API gateways, microservices

4/5

Cloud & DevOps (Kubernetes, Docker)

Direct

Kubernetes, Docker, CI/CD, high availability

4/5

Network Automation & Orchestration

Direct

Infrastructure as code, service orchestration

4/5

Financial Services

Mobile money and payment rails, carrying heavier compliance and reconciliation demands than the rest of the stack.

Financial Services (Mobile Money, Wallets)

Ecosystem

Mobile money, bill payment, airtime transfer

3/5

IoT & Emerging

Device connectivity rather than subscriber connectivity — M2M, eSIM, LTE-M and tracking platforms.

IoT Connectivity (M2M, eSIM, LTE-M)

Ecosystem

M2M, eSIM, fleet tracking, IoT platforms

3/5

Messaging Platforms

The messaging stack itself — gateways, SMSC and SMPP systems, and the A2P traffic that runs across them.

SMS Platform Architecture

Direct

SMSC/SMPP systems, bulk messaging, A2P gateways

5/5

USSD Service Delivery

Direct

USSD gateway, SS7 integration, platform orchestration

5/5

Enterprise Messaging

Integration

CPaaS, API gateways, integration-led deployments

4/5

Voice Platforms

Voice service logic on the switching layer: IVR, portals, ring-back tone and call completion.

Voice Services (IVR, RBT, Voicemail)

Direct

IVR, Ring Back Tone, voice portals, call completion

4/5

Proficiency Scale

Aware

Familiar

Competent

Expert

Master

Experience Tier

Direct

Direct hands-on

Personally engineered / delivered.

Integration

Integration experience

Led or performed integration, not core development.

Ecosystem

Ecosystem familiarity

Adjacent exposure — no overclaim.

Credentials · 08
08Enterprise Credentials

Certified capability, independently verifiable.

The proficiency matrix above is self-assessed. These are not — each credential is issued and revalidated by an external body, grouped here by the capability it certifies.

Cloud

3

Architecture-level certification across all three hyperscalers — the basis for designing hybrid estates without defaulting to a single vendor's answer.

  • AWS SAP

    AWS Certified Solutions Architect — Professional

    Amazon Web Services

  • Azure Architect

    Azure Solutions Architect Expert

    Microsoft

  • Google PCA

    Professional Cloud Architect

    Google Cloud

verifiedCurrent

Security

3

Governance and cloud security certified alongside hands-on network enforcement — policy that can be designed, then actually implemented on the perimeter.

  • CISSP

    Certified Information Systems Security Professional

    ISC²

  • CCSP

    Certified Cloud Security Professional

    ISC²

  • PCNSE

    Palo Alto Networks Certified Network Security Engineer

    Palo Alto Networks

verifiedCurrent

Infrastructure

3

The operating layer certified end to end — host, orchestration and carrier-side network — which is where carrier-grade and regulated workloads are actually kept alive.

  • RHCE

    Red Hat Certified Engineer

    Red Hat

  • CKA

    Certified Kubernetes Administrator

    Cloud Native Computing Foundation

  • CCNP

    Cisco Certified Network Professional

    Service Provider track

    Cisco

verifiedCurrent

Leadership

3

Architecture, delivery and service-management frameworks — the vocabulary enterprise and public-sector procurement runs on, and the structure programmes are audited against.

  • TOGAF

    TOGAF — The Open Group Architecture Framework

    TOGAF 10 Foundation (Part 1)

    The Open Group

  • PMP

    Project Management Professional

    Project Management Institute

  • ITIL

    ITIL — IT Service Management

    ITIL 4 Foundation

    PeopleCert / AXELOS

verifiedCurrent

12 credentials · issued and revalidated by their certifying bodies

Expertise · 09
09Expertise Matrix

Capability architecture, end-to-end.

A working matrix of operational, engineering and strategic capabilities — engineered together rather than as isolated practices.

01

Telecommunications Infrastructure

Carrier networks, VAS, signaling, OSS/BSS, charging & operator-grade platforms.

Practice

Service platforms that live inside a carrier's network rather than beside it: SMPP and SMSC message paths, USSD session logic, voice and IVR services, and the integration seams into charging, provisioning and subscriber data. Correctness outranks throughput here — a mis-rated event or a dropped session is a revenue and regulatory question, not a bug ticket.

SS7 / DiameterSMPP & USSDCharging integration
02

Enterprise Software Engineering

Mission-critical platforms with distributed services, observability and reliability budgets.

Practice

Distributed systems built against a stated reliability budget, where the interface contract, the failure mode and the rollback path are designed before the feature is. Observability belongs to the definition of done: if an incident cannot be reconstructed from telemetry afterwards, the service is not finished.

Distributed servicesReliability budgetsDesign for rollback
03

Cloud & DevOps

Hybrid cloud, GitOps pipelines, IaC, containers, service mesh and platform engineering.

Practice

Platform engineering rather than ticket-driven ops: Terraform and Ansible for provisioning, GitOps for reconciliation, containers and service mesh for the runtime — packaged into a path teams can ship on without filing a request. Hybrid is the assumption, since some workloads never leave the data centre and the pipeline has to treat both targets alike.

Terraform & AnsibleGitOps / ArgoCDKubernetes & mesh
04

Cybersecurity

Zero-trust, identity, network segmentation, threat modeling and compliance programs.

Practice

Security treated as an architecture property: identity as the boundary, segmentation that caps blast radius, secrets held in a vault instead of a pipeline variable, and hardening baselines applied at build time. Threat modelling runs against the design, and compliance is planned as evidence produced continuously — not assembled the week before an audit.

Zero trust & IAMSegmentationHardening baselinesAudit evidence
05

AI Automation

LLM-integrated operations, intelligent workflow systems and ML observability.

Practice

Language models placed where they carry operational load: retrieval over an organisation's own documents and telemetry, assisted triage, and agentic workflows running under scoped permissions. Treated as production software — evaluated against real cases, observed in flight, and given a deterministic fallback for the day the model is confidently wrong.

RAG pipelinesAgentic workflowsModel observability
06

Data Center Architecture

Power, cooling, network topology, rack design and operational runbooks.

Practice

The physical layer every other capability quietly assumes: power and cooling headroom, rack and cabling discipline, topology with no silent single point of failure, and runbooks written for the engineer on shift at 3am rather than for the design review. Capacity is planned against the growth curve, not against this month's bill.

Power & coolingTopology & redundancyRunbook discipline
07

Network Engineering

Carrier-grade routing, MPLS, BGP, SDN/NFV, transport and access layers.

Practice

Routing and transport designed to carrier expectations: MPLS and BGP policy that converges predictably, SDN/NFV where it genuinely reduces hardware dependency, and access-layer design that degrades gracefully instead of failing whole. Change control is part of the engineering — most network outages are configuration events, not equipment failures.

MPLS & BGPSDN / NFVTransport & access
08

Enterprise Systems

ERP-adjacent platforms, integration fabrics, data plane and business orchestration.

Practice

The connective tissue between systems never designed to meet: integration fabrics, event and batch flows, and a data plane where the record of truth for each entity is stated rather than assumed. Business processes are modelled explicitly, so changing one becomes a configuration decision instead of a migration project.

Integration fabricsData plane ownershipProcess orchestration
09

Infrastructure Operations

SRE practice, incident response, capacity planning, 24/7 NOC enablement.

Practice

Running estates as a practice rather than a rota: measured service levels, an incident process with declared severity and a single commander, blameless review that actually changes the system, and capacity planned ahead of the curve. NOC enablement is mostly documentation and drill — the tooling is the easy half.

SRE practiceIncident commandCapacity planning24/7 NOC
10

Strategic Technology Leadership

Org design, technology roadmaps, vendor strategy and executive sponsorship.

Practice

The layer where engineering meets budget: team structure matched to the architecture, roadmaps sequenced by dependency and risk rather than enthusiasm, and vendor strategy that makes switching costs visible before a contract is signed. Executive sponsorship means translating an infrastructure decision into the commercial terms it will ultimately be judged on.

Org designRoadmap sequencingVendor strategy
Capability Lattice
07010603020904080510

Tap or hover a node to name the capability and light up what it depends on.

Every practice above is drawn against the ones it depends on. Network engineering has no meaning without the transport it carries; security is a property of the platform, not a layer bolted to it; leadership is where all of it meets a budget. The matrix is one system with ten entry points.

Sector Operations · 10
10Sector Experience

Operational domains across regulated and large-scale industries.

Confidentiality and NDAs preclude project-level disclosure. The operational footprint is documented at sector level — telecommunications, regulated services, industrial infrastructure and intelligent operations.

01 · domain

Telecommunications

Operator-grade VAS, OSS/BSS, signaling, charging.

Scope

The deepest domain: value-added service platforms sitting directly on carrier infrastructure — SMSC and SMPP messaging paths, USSD and IVR service logic, ring-back tone and content delivery — integrated against OSS/BSS, charging and subscriber systems. Everything is scoped to carrier constraints: signalling correctness, revenue assurance, and change windows measured in minutes.

SMPP / SMSCUSSD & IVROSS/BSS & charging
02 · domain

Healthcare

Regulated systems, clinical data and continuity.

Scope

Systems where both downtime and data handling carry regulatory weight. The emphasis falls on continuity design — redundancy, tested recovery, controlled access to clinical records — and on connecting long-lived on-premise applications to modern platform layers without breaking the compliance posture around them.

Continuity designAccess controlLegacy integration
03 · domain

Enterprise Operations

Mission-critical platforms across business lines.

Scope

Platforms the business cannot run a day without: integration fabrics between finance, operations and customer systems, service levels that are defined rather than assumed, and observability wired in before go-live instead of after the first outage. The engineering question is rarely the feature — it is what happens on the worst day of the quarter.

Integration fabricsReliability budgetsObservability
04 · domain

Education Technology

Scalable learning and assessment infrastructure.

Scope

Campus-scale infrastructure with sharply peaked load — enrolment, assessment and results windows where a semester's credibility rests on a few hours of uptime. Scope extends past the systems into the procurement mandate itself: specification, vendor evaluation, deployment and post-implementation support for academic institutions.

Peak-load capacityCampus infrastructureProcurement mandate
05 · domain

Industrial Infrastructure

OT/IT convergence and operational automation.

Scope

Where operational technology meets enterprise IT — the hard part being segmentation and safe data flow between two networks with entirely different lifecycles, patch tolerances and failure consequences. Automation is introduced on the IT side of that boundary first, with the OT side treated as a controlled dependency rather than a target.

OT/IT segmentationOperational automationControlled boundaries
06 · domain

Cloud Systems

Hybrid landing zones, platform engineering.

Scope

Hybrid estates rather than clean-slate cloud: landing zones, identity and network design that let regulated workloads stay on-premise while everything else takes the elasticity. Delivered as platform engineering — Kubernetes, Terraform and GitOps pipelines handed to teams as a paved road, not as a pile of credentials.

Landing zonesKubernetes & IaCGitOps delivery
07 · domain

Smart Operations

AI-integrated workflows and intelligent runbooks.

Scope

Operations with a reasoning surface: retrieval over an estate's own documentation and telemetry, LLM-assisted triage, and agentic workflows that absorb the repetitive half of an incident. Governed like infrastructure — scoped permissions, an audit trail, and a defined fallback for when the model is wrong.

LLM-assisted triageRetrieval over telemetryAudited automation
08 · domain

Digital Transformation

Modernisation roadmaps and execution.

Scope

Modernisation judged by what actually gets decommissioned, not by how many slides it produces. Sequence carries the programme: dependency map first, then phased migration behind stable interfaces, on a roadmap that the finance and operations sides can both sign without a translation layer.

Dependency mappingPhased migrationExecutable roadmaps
09 · domain

Logistics Intelligence

Movement, traceability and decision systems.

Scope

Following assets and shipments end to end — fleet and IoT telemetry, traceability records that survive an audit, and decision systems that turn location and status data into dispatch actions. Connectivity is the binding constraint, so designs assume intermittent links and reconcile once the link returns.

Fleet & IoT telemetryTraceabilityOffline-tolerant design
10 · domain

Infrastructure Automation

IaC, policy-as-code, autonomous operations.

Scope

Taking manual steps out of the paths that break things: infrastructure as code for provisioning, policy-as-code for the guardrails, and pipelines where an environment is rebuilt from a repository rather than from memory. The honest measure is how much of that rebuild completes with nobody at the keyboard.

Terraform & AnsiblePolicy as codeRebuild from repo
Infrastructure · 11
11Stack & Infrastructure

A working operations center for telecom, cloud and enterprise systems.

The technology surface is intentionally broad: carrier-grade telecom, hybrid cloud, Linux infrastructure, AI integration and security architecture — selected and operated with engineering rigour.

Cloud & Platform

layer · 01
Approach

Multi-target out of necessity rather than preference: public cloud where elasticity pays for itself, OpenStack and VMware where a workload is bound to a data centre by regulation or latency, and Kubernetes as the common runtime that keeps the deployment story identical across both. Platform choice follows the workload's constraints — data residency, egress cost, failure domain — not a vendor relationship.

  • AWS
  • GCP
  • Azure
  • Kubernetes
  • OpenStack
  • VMware
  • Proxmox
statusOperational

DevOps & Automation

layer · 02
Approach

Terraform describes what should exist, Ansible converges what is already running, and ArgoCD reconciles the cluster against the repository — so the repo, rather than someone's terminal history, is the source of truth. Pipelines are kept deliberately boring: reproducible builds, promotion between environments, and a rollback that has been executed at least once before it is needed.

  • Terraform
  • Ansible
  • GitOps / ArgoCD
  • Jenkins
  • GitHub Actions
  • Helm
statusOperational

Linux & Infrastructure

layer · 03
Approach

The layer where performance problems are actually solved: distribution chosen for support lifecycle rather than familiarity, systemd units used deliberately for isolation and restart behaviour, kernel and networking parameters tuned against measurement, and Ceph where storage has to scale horizontally without a proprietary controller. Hardening is applied at image build, not after deployment.

  • RHEL / Rocky
  • Debian / Ubuntu
  • Systemd
  • Networking Stack
  • Storage / Ceph
statusOperational

Telecom & Network

layer · 04
Approach

Carrier-side competence across both planes: MPLS and BGP carrying transport and policy, SS7 and Diameter for signalling and interworking with legacy core elements, and SDN/NFV where functions can genuinely move off dedicated hardware. Everything terminates in OSS/BSS — a service that cannot be provisioned, rated and billed is not yet a service.

  • MPLS
  • BGP
  • SDN / NFV
  • SS7 / Diameter
  • 5G Core Concepts
  • Carrier OSS/BSS
statusOperational

AI & Data

layer · 05
Approach

Retrieval-grounded systems in preference to fine-tuned ones wherever the knowledge moves faster than a training cycle: documents and telemetry indexed into vector stores, prompts and tools versioned like code, and evaluations run against captured real cases before a change ships. Observability covers cost and latency alongside answer quality, since an unwatched model becomes an unbounded bill.

  • LLM Integration
  • RAG Pipelines
  • Vector Stores
  • MLOps
  • Observability
statusOperational

Security

layer · 06
Approach

Identity first: SSO and scoped roles as the real perimeter, Vault holding secrets that pipelines fetch at runtime instead of storing, and hardening baselines encoded so a fresh host starts compliant rather than being remediated into compliance. SIEM and SOC workflows close the loop — detection only counts when someone owns the alert and the response path is written down.

  • Zero Trust
  • IAM / SSO
  • Vault
  • SIEM / SOC
  • Hardening Baselines
statusOperational
Vision · 12
12Leadership & Vision

Building globally competitive technology enterprises originating from Bangladesh.

The long-horizon thesis: combine South Asian engineering capacity with international delivery discipline, regulated-industry rigour and AI-integrated operations — and operate them at global standard.

01Vision Pillar

Build globally competitive technology enterprises from Bangladesh

Engineering operational excellence that competes on the global stage — combining South Asian engineering capacity with international delivery discipline.

Rationale

South Asian engineering capacity has largely been sold by the hour into someone else's product. The alternative being built here is ownership — entities that hold the platform, the delivery method and the customer relationship: i-VAS Solution on the carrier and VAS side, FAR INTEL Bangladesh on enterprise and infrastructure engineering. “Global standard” is not a marketing line but a delivery discipline: written architecture, tested rollback, measurable uptime and an audit trail that survives an enterprise procurement review.

Owned platforms, not billed hoursInternational delivery disciplineTwo operating entities
02Vision Pillar

Operational intelligence as core infrastructure

AI-integrated operations are no longer optional. Every layer of the stack — telecom, cloud, enterprise — gets a reasoning surface.

Rationale

Carrier networks and enterprise platforms already emit far more telemetry than any operations team can read. The bet is that the next decade of infrastructure work is not more dashboards but reasoning placed inside the runbook — LLM-integrated operations, retrieval over the estate's own documentation, and agentic workflows that absorb the routine half of an incident. It is treated as an infrastructure layer with the same obligations as any other: observability, access control and a defined failure mode.

LLM-integrated operationsRetrieval over the estateAgentic runbooksGoverned by design
03Vision Pillar

Sovereign-grade digital infrastructure

Data centers, networks and platforms built for jurisdictional resilience, regulatory compliance and long-horizon continuity.

Rationale

Regulated operators — telecom, healthcare, public institutions — increasingly cannot answer basic questions about where their data physically sits or who can compel access to it. Sovereign-grade means the answer is designed in rather than discovered during an audit: in-country capacity with documented power, cooling and topology; network paths that survive a single-vendor failure; and platforms that meet local regulatory obligations without a foreign dependency in the critical path. Continuity here is planned in decades, not contract terms.

In-country capacityJurisdictional resilienceRegulatory complianceDecade-scale continuity
04Vision Pillar

Ecosystem and partnership architecture

Investing in operators, integrators and product teams — assembling an ecosystem rather than isolated bets.

Rationale

Infrastructure is never delivered by a single company. A carrier programme needs the platform vendor, the integrator, the local delivery team and the procurement path to move together — so the position is built across that chain rather than from one seat in it. The structure has been exercised in practice: operator engagements across South and Southeast Asia, and end-to-end technology procurement mandates for universities and public institutions run from solution design through to post-implementation support.

Chain-wide positionsOperator & integrator alignmentEnd-to-end procurement

Infrastructure is the substrate of every modern economy. Building it well — sovereign, intelligent, resilient — is the work that compounds.

— Syed Omar Ibn Feroj
Capital · 13
13Investments & Strategic Operations

Operator capital. Strategic positions. Ecosystem leverage.

Beyond operating entities, the work extends into strategic capital and ecosystem-building — backing infrastructure-anchored ventures with operator depth, not just term sheets.

Thesis · 01

Strategic Operator Capital

Backing infrastructure-anchored ventures with operator depth, not just term sheets.

Abstract

Capital goes where the underlying asset is infrastructure — carrier platforms, data-centre capacity, integration layers — rather than consumer distribution. Diligence runs the same questions an operations review runs: what fails under load, what the platform costs per unit at scale, and who owns the escalation path at 3am. What follows the cheque is architectural review, vendor leverage and carrier access built across South and Southeast Asia — not board-meeting commentary.

Infrastructure-backed assetsOperator-grade diligencePost-investment engineering
Thesis · 02

Technology Ecosystem Building

Long-horizon positions in companies that compound through platform leverage.

Abstract

A platform company is worth more when it sits beside an integrator, a connectivity layer and a delivery team that can actually install it — so positions are taken with the surrounding ecosystem in view. The preference is for businesses whose value compounds inside other people's roadmaps: APIs, protocols and channel positions that grow harder to displace with every integration shipped.

Platform leverageIntegration & channel positionCompounding defensibility
Thesis · 03

Scalable Operational Frameworks

Investing in repeatable systems — deployment, security, observability — across the portfolio.

Abstract

The repeatable advantage is operational, not commercial. Deployment pipelines, hardening baselines, observability and incident practice are treated as shared infrastructure — built once, proven in production, then handed across companies instead of being re-invented badly at each stage. That is the difference between a capable engineering team and a company that can carry regulated, carrier-grade workloads on contract.

Deployment & IaCSecurity baselinesObservability & SRE practice
Thesis · 04

Founder & Engineering Partnership

Hands-on partnership with founders on architecture, hiring, infrastructure economics and go-to-market.

Abstract

Involvement is technical and hands-on: architecture review before the rebuild, hiring calibration for the first infrastructure engineers, honest numbers on cloud and data-centre economics, and introductions timed to when a procurement cycle actually opens. The bias runs toward founders working unglamorous problems in telecom, industrial and regulated markets — where buyers move slowly, contracts run long, and depth outlasts speed.

Architecture reviewHiring & org designInfrastructure economicsProcurement access
Open Knowledge · 14
14Knowledge Archive

Open knowledge repository — notes, publications & engineering writings.

A continuously expanding archive of free, public-facing technical notes — JavaScript, DevOps, Linux, AI, cloud, telecom and enterprise automation. Engineering thinking in the open.

HTML5 Canvas 28 chapters

HTML5 Canvas — Engineering Notes for Pixels

A working Canvas 2D reference — the immediate-mode model, paths and transforms, pixel manipulation, a correct animation loop, hit-testing, and the high-DPI and performance details that decide whether it's smooth.

Abstract

Twenty-eight chapters on the Canvas 2D API: context setup, the coordinate system and high-DPI handling first, then rectangles, paths, curves and arcs, fills and strokes, gradients, patterns, shadows, line styles, text, images and sprites. The second half is the moving part — transforms and save/restore, compositing, clipping, pixel manipulation, a correct animation loop, redraw strategy, hit testing, particles, performance and export — ending on when to reach for SVG or WebGL instead.

2D APITransformsAnimationPerformance
LiveRead

Repository continuously expanding · Direct links coming online

Engage · 15
15Strategic Contact

Executive-level access. By introduction or direct channel.

Engagements are evaluated on strategic fit. Enterprise, operator, investor and partnership inquiries are welcome through the channels below.

Inquiry Console · Secure
Inquiry Window

Please use an official organisational email — free webmail is not accepted.

Submissions are relayed securely to omar@i-vas.net. Long briefs can also be sent by email.

Digital Business Card

Scan, share, save to contacts

One scan writes every channel on this page into your address book.

LinkedIn

linkedin.com/in/omarbhaii

Professional record and current roles — the fastest route to a warm introduction.

Email

omar@i-vas.net

Primary written channel for briefs, documents and long-form scope.

Phone

+8801876222999

Direct line for time-sensitive operator and partnership matters, Dhaka business hours.

Base of Operations

Dhaka, Bangladesh

Dhaka-based, working across South and Southeast Asian markets.

Engagement Policy

Strategic partnerships, investor introductions and operator-grade engagements are welcome. Project-level disclosures are governed by NDA; sector-level conversations begin without one.