Web Development Company in Ho Chi Minh City

A Ho Chi Minh City web number follows localisation and performance obligations rather than page count, and each scoped phase carries a fixed fee, not a published band. A focused marketing or campaign site is a six to ten week engagement covering Vietnamese localisation with tone-mark integrity, a CMS choice (Strapi, Sanity, or Contentful), Core Web Vitals tuning for the Vietnamese device mix, and a PDPD-aligned cookie consent flow. A full headless e-commerce build (Tiki or Sendo seller portal-grade) adds multi-locale support, NAPAS plus wallet trio checkout, and MIC e-commerce decree compliance. Bank or e-money portal-grade builds add SBV Circular 23/2022 cybersecurity controls, Decree 53 in-country deployment at Viettel IDC or FPT Smart Cloud, and full WCAG 2.1 AA accessibility. Our rates run below the Vietnamese in-country market premium for senior full-stack engineers because of the Chandigarh delivery base, while keeping near-perfect Saigon overlap. We quote fixed fee on scoped phases.

Decree 53/2022 defines when foreign service providers must store Vietnamese user personal data inside Vietnam and establish a local representative office, with triggers including e-commerce, online payments, social networking, OTT communications, online advertising, telecoms, and cloud services. For web workloads the practical questions are which user data the site captures, where it sits at rest, and whether the in-country trigger applies. Our discovery produces a Decree 53 data-flow map and a residency decision: AWS ap-southeast-1 (Singapore) cross-border with documented contractual safeguards for low-sensitivity workloads, or in-country storage at Viettel IDC (the Viettel Group cloud arm, the largest in-country provider), VNPT Data, or FPT Smart Cloud for workloads where the in-country trigger applies. CDN choices similarly: Cloudflare, AWS CloudFront, and Akamai for global, Viettel CDN and BizFly CDN for in-country acceleration when Decree 53 favours an in-country posture. We document the architecture so MIC and MPS have a clear answer.

Vietnamese is a tonal language written in a Latin-derived script with diacritical marks across six tones plus the đ character. UTF-8 with full tone-mark integrity is non-negotiable; we have audited too many vendors who shipped broken diacritics on tier-2 hardware or under aggressive font subsetting. Font selection covers all tone combinations cleanly (Inter, Roboto, Noto Sans, and Be Vietnam Pro are our defaults), line-length tested for around 15 to 25 percent expansion versus English source strings, and search relevance tuned for Vietnamese-language tokenisation (which behaves differently from English under standard Lucene-based search; we use Elasticsearch with Vietnamese analyser plugins or Algolia with Vietnamese locale where the use case warrants). Northern Hanoi versus Southern Saigon register is handled where the audience demands it. Native Vietnamese reviewers in our Chandigarh hub work directly with Saigon client teams, and English is the secondary track, not the source of truth.

The National Public Service Portal (dichvucong.gov.vn) and the city-level dichvucong.hochiminhcity.gov.vn establish the canonical Vietnamese gov-web pattern: single sign-on against the National Public Service Account, electronic signature via the Vietnamese PKI hierarchy (VNPT-CA, Viettel-CA, FPT-CA, and BKAV-CA as the qualified providers), Citizen Identification Card chip integration for eKYC, and document-workflow patterns that map to the offline gov-services experience. For gov-adjacent web (provincial portals, ministry sites, public-utility branding) we build to this pattern with .NET as the dominant stack (matching the existing gov contractor estate from FPT, Viettel, VNPT, and BKAV), SSO integration with the National Public Service Account where contracts permit, and accessibility against WCAG 2.1 AA with Vietnamese-language screen-reader validation. We coordinate openly with the established gov contractor where the contract requires it.

Vietnamese connectivity is excellent in HCMC, Hanoi, Da Nang, and the major industrial parks, with Viettel, VNPT, Mobifone, and Vietnamobile delivering 4G at competitive speeds and 5G rolling out in HCMC and Hanoi from 2024 to 2025. Connectivity is patchy in tier-2 cities (Can Tho, Hue, Nha Trang, Quy Nhon, Hai Phong outside the urban core), the Mekong Delta, the Central Highlands, and the rural north. Web budgets that assume HCMC-grade connectivity lose users outside the urban core. We target LCP under 2.5s on 4G connections from tier-2 city devices, INP under 200ms on the mid-tier Vietnamese device baseline (Samsung Galaxy A14, Vivo Y22, Oppo A38, Xiaomi Redmi 12), CLS under 0.1, and aggressive JS bundle budgets (typically under 180KB compressed first-load for content-heavy and under 300KB for commerce). Static site generation and ISR where the use case permits, with image optimisation through next/image, AVIF and WebP, and lazy-loaded video below the fold.

Yes. SBV Circular 23/2022/TT-NHNN (effective from 2023) sets the cybersecurity requirements for credit institutions, e-money providers, and intermediary payment service providers in Vietnam, building on Circular 18/2018 and aligning with the wider Vietnamese Cybersecurity Law of 2018 plus Decree 53/2022. For web portals the practical obligations include strong authentication for customer-facing and internal users, encryption at rest and in transit, vulnerability management and pen-testing cadence, third-party-risk discipline (which we document as the vendor), incident response with defined SBV reporting timelines, and a documented secure-development lifecycle. We build SBV Circular 23/2022-compliant portals with OWASP ASVS Level 2 (or Level 3 for the wallet trio and bank-grade flows) as the baseline, threat modelling against the OWASP Top 10 plus Vietnamese-specific phishing and ATO patterns, and pen-testing through SBV-recognised independent assessors before launch. We coordinate with your internal infosec team and the SBV-recognised pen-test vendor.

Vietnamese web checkout is a layered payments problem. NAPAS routes instant interbank against the SBV-overseen national switch (NAPAS 247 as the consumer-facing brand). MoMo, ZaloPay, and ShopeePay (the wallet trio) cover standalone e-money. VNPay QR provides merchant acceptance through scannable QR. We integrate the full set: NAPAS top-up flow for users funding the merchant directly from a linked bank, the wallet trio with QR-display checkout and deep-link to the wallet app on mobile web, VNPay QR for in-store or kiosk-adjacent flows, and direct bank API integration with Vietcombank, BIDV, VietinBank, Techcombank, MB Bank, ACB, TPBank when the merchant has bank-level relationships. Apple Pay and Google Pay are partial-coverage and remain secondary to the wallet trio. International cards (Visa, Mastercard, JCB) through your acquirer, with 3DS 2.0 for SCA. NF-equivalent Vietnamese e-invoicing (hoa don dien tu) is wired into the commerce flow where the merchant requires it.

There are excellent Saigon web studios, and for some briefs they are the right answer; we will say so. We compete where the buyer wants international delivery discipline (data-flow maps, SBV plus PDPD documentation that holds up to a Singapore, Seoul, or US head office), where Vietnamese in-country senior full-stack specialists are priced at a premium because of FPT, TMA, KMS, VNG, and the export-engineering compression on senior comp, or where the client needs night-shift overlap with US headquarters that Chandigarh plus Edmonton delivers natively. Our Chandigarh hub is 1.5 hours behind Saigon with near-perfect overlap and senior full-stack rates below the Vietnamese in-country market premium. Same-day standups, not overnight handoffs. For gov-adjacent contracts where the local FPT, Viettel, or VNPT prime is mandated, we partner cleanly with the prime.