Jamstack Development in Singapore
We are an Indian engineering team working with businesses in Singapore. Written scope before any code, and a fixed quote in SGD.
Working hours
Our day runs 09:00 to 18:00 India time, which is 11:30 to 20:30 in Singapore, so from late morning onwards we are on the same working day, and anything you raise first thing is picked up by 11:30.
Quoted in SGD
Quotes exclude the 9% GST in Singapore, shown separately on the invoice.
Data protection
Work for this market is scoped against the Personal Data Protection Act 2012 (PDPA), agreed before development starts rather than retrofitted afterwards.
Written scope
Every engagement starts with a written scope and a fixed SGD quote within 24 hours, so the price is set before work begins.
About Jamstack Development
We build Jamstack sites: pages pre-rendered at build time and served from a CDN, content in a headless CMS your team can edit, and the dynamic parts handled by APIs. The result loads fast, has a small attack surface, and hands Google clean HTML to index. Senior engineers in Noida, a written scope, and a flat quote before any code.
What the engagement includes
- Next.js for static generation (SSG) and incremental static regeneration (ISR), so most pages are pre-built and content updates re-generate the affected pages without a full rebuild.
- A headless CMS chosen for how your editors actually work: Sanity, Contentful, Strapi, Storyblok, or headless WordPress. The content model is designed around your team, not a template.
- Headless commerce through Shopify's Storefront API or a similar backend for cart, checkout, and inventory, with the storefront built separately for speed and design freedom.
- Edge and CDN delivery on Vercel, Netlify, or Cloudflare, so pages are served from a node near the visitor instead of one origin server everyone hits at once.
- Serverless functions for the dynamic parts: contact forms, site search, newsletter signup, and webhooks, without standing up and babysitting a full server.
- Image optimization, structured data, XML sitemaps, and Core Web Vitals work built in from the start, because a fast site Google can read cleanly is the entire point of choosing Jamstack.
POFMA directions, photo credits and the move to Isomer Next: a Jamstack site in Singapore
A Jamstack site publishes by rebuilding, and in Singapore the law can put a deadline on that rebuild. Under the Protection from Online Falsehoods and Manipulation Act 2019, a Correction Direction requires whoever communicated a statement to put out a correction notice in the specified form and manner by the specified time, and section 11(3) lets it require that notice in specified proximity to every copy of the statement, or of a substantially similar one, that the person communicates in Singapore. A Stop Communication Direction under section 12 goes further, and the Act defines stopping as taking the steps needed so the statement is no longer available on the internet to end-users in Singapore, removing it from an online location if necessary. Either can be issued to a person outside Singapore. Section 15 makes failing to comply an offence, with a fine of up to S$20,000, 12 months' imprisonment or both for an individual and up to S$500,000 for anyone else, and having applied to vary the direction or appealed is no defence. On a static site the article is rarely in one place. The same text sits in listing pages, the RSS feed, a JSON search index shipped to the browser, generated social images and every CDN edge, so a correction is one content field that every template renders, followed by a full rebuild and a cache purge, not a notice pasted into a single page. Immutable deploys are the trap. Every successful Netlify deploy gets a permalink whose content never changes, and Vercel's generated deployment URLs are publicly reachable by default unless deployment protection covers them, so a withdrawn article can stay live at an old deploy address after production is clean. We protect or delete past deployments that carried it and keep the whole path as a rehearsed runbook. Whether a statement falls within the Act is for your own counsel.
Singapore gave creators a statutory right to be credited when the Copyright Act 2021 took effect on 21 November 2021, and a headless CMS is where that right is kept or quietly lost. Section 371 gives the author of an authorial work the moral right to be identified, and section 372 requires anyone who publishes an artistic work, a photograph included, or communicates a visual image of it to the public, to identify the author. Section 373 says how: in the way the author has asked, a pseudonym for example, where that is reasonable, and always clearly and with reasonable prominence, which for a web page means likely to be noticed by the person viewing it. A credit that exists only in alt text or in the file's metadata does not meet that. The right has edges worth knowing. Section 375 leaves out computer programs and works made by employees whose employer first owns the copyright, and section 382 lets an author consent, in writing or otherwise, or formally waive the right in a signed written waiver. A separate set of provisions protects the credit inside the file. Sections 409 to 411 treat information identifying a work, its author or owner and its terms of use as rights management information, and a person infringes by knowingly removing it without authority where they know or ought reasonably to know that doing so will facilitate or conceal an infringement. Jamstack image pipelines remove it by default: sharp, the library behind most build-time and on-demand image optimisation, strips all metadata unless told otherwise. So each image asset in the CMS carries its creator, the credit as they wish it shown, the licence terms and any waiver on file, templates print the credit beside the image, and the pipeline keeps copyright and creator fields on licensed photographs as a deliberate exception. Whether a particular use needs a credit is for your own counsel.
If the buyer is a ministry, statutory board, school or public healthcare institution, the first Jamstack question in Singapore is why the site is not on Isomer. Isomer is the website builder Open Government Products runs for agencies, and it is itself a Jamstack platform: the current version, Isomer Next, builds each site with Next.js as a static export, and its pitch to agencies is no tenders and no AORs, with IM8 and VAPT covered. Isomer Classic, the earlier version built on Jekyll and GitHub, was retired from 30 September 2026, with all whole-of-government and public healthcare sites told to migrate by September unless another arrangement was made. So as of this month a public site still on Classic is either under a separate arrangement or about to be rebuilt, and that changes what an outside build has to justify. A custom static site for an agency carries the work Isomer absorbs, meaning the agency's IM8 obligations, a vulnerability assessment and penetration test before launch, and hosting the agency's IT department will accept. It earns its place where the content model or the interaction outgrows Isomer's prescriptive templates, such as an eligibility checker, a calculator or a data-heavy explorer, not where the brief is a standard information site. Where Isomer fits, the honest advice is to use it, and the useful outside work becomes what surrounds it: migrating content from the old site with every redirect mapped, or a separate interactive tool the Isomer site links to. Launch has a Singapore choreography of its own. Government domains are managed in the whole-of-government ITSM portal, reachable only from GSIB laptops, so the agency's IT department changes the CNAME and A records at a booked time, with the TTL set to five minutes, and Isomer recommends launching between 10.30am and 4.30pm on a weekday. Which platform a public site belongs on is the agency's decision.
How we work with Singapore clients
Singapore is the one market we serve where the working day is simply shared. We are two and a half hours behind you and neither country moves its clocks, so our morning starts partway through yours and the whole of your afternoon is live time for both sides. That changes the shape of an engagement more than anything technical does: a call is booked for the same afternoon rather than the same week, a question raised before your lunch is answered after it, and the written-first method we run for North American clients is a courtesy here rather than a necessity. We keep the written record anyway, with a default chosen on every open decision, because it is the thing an auditor or a new hire can read later and a call is not.
Invoicing is worth stating plainly because the GST position confuses buyers on both sides. We are outside Singapore, so no GST appears on our invoice. Whether you account for it yourself is the reverse charge question, and IRAS's own guidance is that a GST-registered business making only taxable supplies is not affected, while a partially exempt one accounts for it in its own return. We quote in Singapore dollars, the figure holds for the project whatever the rupee does, and payment by bank transfer or Wise avoids the card fees a five-figure invoice does not need. The contract can sit under Singapore law with Singapore courts, and unusually among our overseas markets that clause has teeth: Singapore is a reciprocating territory under section 44A of India's Civil Procedure Code, so a judgment of the Singapore High Court can be executed in India directly rather than re-litigated.
Full service detail
This page covers how we work with clients in your market. The complete Jamstack Development page, with the full technical detail, process and frequently asked questions, is written in English.
Read the full service page (English)Questions Singapore clients ask
How does GST work if you are based in India?
No GST is charged on our invoice, and the invoice says so. Whether you account for it under reverse charge depends on your input tax position: IRAS's guidance is that a GST-registered business making only taxable supplies is not impacted, a partially exempt business or one with non-business receipts accounts for GST on imported services in its own return, and a business that is not registered should ask its accountant, because an exempt business importing more than S$1 million of services in a year can be required to register. We would rather your accountant confirmed your position before the first invoice than reconciled it at year end.
Are you compliant with the PDPA?
We build to it rather than claiming a certificate. The consent, purpose limitation and notification obligations shape the forms and the data model; retention limitation means records are deleted on a schedule rather than kept indefinitely; access and correction requests are features with a queue behind them rather than a manual database job. Processing happens in India, so the transfer limitation obligation applies, and the processor agreement we sign sets out the comparable standard of protection the Act asks for. The obligation to design for early is breach notification: an organisation has three calendar days from determining a breach is notifiable, which means one likely to cause significant harm or one affecting 500 or more people, to tell the PDPC, and answering what was in the breach is only possible if the logging existed beforehand. Appointing a Data Protection Officer is your obligation rather than ours, and we will say so if a design choice would make that person's job harder.
Can we use a PSG or EDG grant to pay for this?
Not PSG. The Productivity Solutions Grant funds pre-scoped packages from pre-approved vendors for Singapore-registered companies, and a custom build from an overseas team is not that shape, so we will not pretend it is. The Enterprise Development Grant is assessed project by project against its own criteria, and whether a build like yours qualifies is a question for Enterprise Singapore or your grant consultant to answer before the scope is written rather than after a budget has assumed it.
We are regulated by MAS. Can you meet the outsourcing requirements?
We can supply what a due-diligence pack asks for, accept audit and access rights in the contract, and name every sub-processor that touches your data. What we will also tell you in the first conversation is what we do not hold: we are not SOC 2 or ISO 27001 certified, and our security page says so in those words. Whether an engagement with us is a material outsourcing arrangement under the MAS guidelines, and what that requires of you, is your compliance team's determination, and it changes the contract before it changes the code, so it belongs in week one.
Jamstack Development: common questions
What is Jamstack development, in plain terms?
It is a way of building sites where the pages are pre-rendered into HTML ahead of time and served from a CDN, instead of a server building each page from a database on every request. Dynamic bits like forms, search, and carts run on top through APIs. The payoff is a site that loads fast, is cheaper and safer to host, and gives search engines clean HTML to read. The name stands for JavaScript, APIs, and Markup.
Is Jamstack good for SEO?
Yes, and it is one of the main reasons to choose it. Because pages are pre-rendered, a crawler gets finished HTML immediately instead of waiting on JavaScript to build the page, and CDN delivery keeps load times low, which helps Core Web Vitals. We build in sitemaps, structured data, and clean URLs from the start. It is not magic that ranks a brand new site overnight, but it removes the technical excuses so content and authority can do their job.
Can my team still edit the site without calling a developer?
Yes. Content lives in a headless CMS such as Sanity, Contentful, Strapi, Storyblok, or headless WordPress, and your editors change text, images, and pages there in a normal editing interface. With incremental regeneration, an edit re-builds only the affected pages, so updates go live quickly without a developer running a full deploy. We also set up preview so editors can see a change before it is public.
Can you do e-commerce or an online store on Jamstack?
Yes. We build headless storefronts where Shopify (or a similar commerce API) runs the cart, checkout, inventory, and payments, and a custom Next.js front end handles the design and the pages customers browse. You keep a proven commerce engine and get a faster, more flexible storefront than a stock theme allows. For very large or highly custom checkout logic we will scope it honestly, since headless commerce adds moving parts worth planning for.
Can you migrate my existing WordPress site to Jamstack?
Yes, and it is common work. We can put a Next.js front end in front of your existing WordPress so your team keeps editing where they know, or move the content into a modern headless CMS entirely. Either way we map your existing URLs and redirects carefully so the rankings and links you have already earned carry over rather than breaking on launch day.
Other markets we work in
Tell us what you are building in Singapore
Send the scope, or just the problem. You get a written scope and a fixed SGD quote back within 24 hours, from the engineers who would do the work.