What's all this 'JAM' in JAMstack



All the content fetching and generation, at build time, is handled by JavaScript. This could be any front-end framework like Vue.js, React, Angular, etc. or even, our favorite, vanilla JavaScript.



All server-side processes or database actions are abstracted into reusable APIs, accessed over HTTP with JavaScript. These can be custom-built or leverage third-party services.



Templated markup should be pre-built at deploy time, usually using a site generator like 11ty, Nuxt.js, or Hugo for content sites, or a build tool like Webpack, or ParcelJS for web apps.


Why should anyone care?

Whoever has been involved in WordPress server management knows the pains of making the server secure. Scaling and speed are different issues altogether.
Now try to imagine a world without all that...


Security of static websites

Generally, static sites are more secure than dynamic sites. In most cases, they are much more secure.

  • Fewer attack vectors to explore, no database, no WordPress or any other CMS.
  • The site is hosted on CDN caching servers, so what would one even try to hack?
  • CDN provides SSL/TLS encryption and DDoS attacks protection.

Scalability, Reliability, Redundancy

A CDN eliminates the guessing game in determining how many servers are needed to meet traffic needs. The website is distributed across many servers around the world and visitors will be directed to the server closest to their location, rather than your main web server, ensuring that your site is fast and available to users across the globe. This technology provides:

  • Load Balancing
  • Edge Servers Failover
  • Data Replication

Significantly improved load times

It’s true. Just a 2-second delay in page load time can increase bounce rates by up to 103%. So we did this:

  • Distance reduction – reduce the physical distance between a client and the requested data
  • Static content only – no "moving parts" like database or CMS, no processing, just serving pre-generated static files and assets.
  • Reduced data transfer – employ techniques to reduce file sizes so that initial page loads occur quickly

Which CMS is best for you?

Choosing the right CMS is crucial. Our CMS selection is targeting three types of publishers, providing the best in breed for each publisher type so that you can just focus on your content creation workflow.

  • Ghost(Pro) - News portals and high volume publishers look no further - speed, excellent built-in SEO, content monetization, and Fastly CDN included. Monolithic or headless configuration, your choise.
  • Hygraph - Powerful headless CMS for publishers with serious customization, structured data, and content modeling requirements. CDN included.
  • Sanity - Possibly the best solution for managing structured and omnichannel content, making it a great platform to build any digital product on top of. CDN included.

We'd be glad to hear from you. No strings attached.

I agree with Privacy Policy and Terms Conditions