Entle Web Solutions
Background image of red dots in a horizontal helix shape

Entle Core™ enables lightning-fast, enterprise-ready websites

Entle Core™ combines a serverless architecture, a supercharged static site generator, and a CI/CD pipeline to unlock new value.

See how it works
A screenshot of a PageSpeed score showing 94/100 for performance and 100/100 for accessibility, best practices, and SEO

A proven, serverless architecture

Traditional websites, such as those powered by WordPress, rely on backend servers that dynamically respond to visitors' request. These servers need to be monitored and maintained, they are vulnerable to attacks, and they are hard and expensive to scale.

Scroll to the right to see more:

Visitor
CDN
Web server
App server
CMS
Database

Entle Core™ websites are serverless. Instead of having backend servers dynamically responding to visitors' requests, Entle websites are built to static files whenever their content changes. These static files are served directly from AWS' battle-tested S3 storage and Cloudfront CDN. Any required dynamic functionality is provided by serverless AWS Lambda functions.

Powered by AWS
Visitor
Storage and CDN
Serverless functions
 
 
Website deployed
on changes
CMS

Scalable by design

Serverless storage like AWS S3, functions like AWS Lamda, and CDNs like AWS Cloudfront are designed for massive scalability. Websites built on them benefit from scalability out of the box, without the need for complicated, expensive, self-maintained server setups.

Secure by design

Traditional backend servers have a large attack surface; they require constant tweaking to keep secure. Serverless websites are static resources, which have dramatically reduced attack surface. Serverless functions also run in highly secure, isolated environments.

More robust

Unlike a traditional architecture where backend problems easily spill into the frontend, a serverless website's frontend is completely decoupled from its CMS and source code; errors introduced there are prevented from going live to the frontend by the deployment pipeline.

Reduces risk

Risk is dramatically reduced by being able to rely on AWS S3, Lamda, and Cloudfront — the same Amazon-managed services used by thousands of other enterprise customers — instead of designing, testing, and maintaining one's own server setup.

Whitepaper: How Entle Core™ reduces risk with proven technologies

Read more about the battle-tested technologies and services underlying Entle Core™ websites, as well as major companies relying on the same technologies.

Download whitepaper

Supercharged static sites, tested and deployed on changes

Entle Core™ follows the JAMstack (JavaScript, APIs, and Markup) pattern: whenever your website's content and source code change, the site is rebuilt in minutes into optimised resources with a static site generator. Then, it is deployed to decoupled infrastructure, with static resources served from AWS S3 and Cloudfront and dynamic functionality handled by serverless AWS Lamda functions.

CMS content
Source code
Built with
11ty + Entle Core™
Static files
Functions
Tested and deployed with
Entle Core™ CI/CD
S3 + CF
Lamda

Entle Core™ plugs into Eleventy (11ty), one of the most performant JAMstack static site generators, to build websites into static files. Other notable high-traffic websites powered by Eleventy include web.dev (the foremost online guide to web performance), Netlify, MIT, and Google Chrome OS, among others.

Entle Core™ adds a suite of automatic build optimisations to 11ty to further enhance performance, optimise for SEO, and enforce best practices. From small details like ensuring target=_blank safety to large tasks like heavily optimising images, JS, and CSS, Entle Core™ supercharges your website.

Entle Core™ catches errors early with a custom CI/CD pipeline. Whenever your website's content or source code is updated, the website is rebuilt, tested, and deployed in minutes. If any errors are introduced, they are caught early and prevented from going live to your public-facing website.

Flexible content management and integrations

Content can be pulled into an Entle Core™ website from nearly any source when the site is rebuilt. Entle websites come standard with Netlify CMS for content management, which is easy to learn, secure, and allows every change to the content to be shown in a unified audit log. However, the decoupled nature of Entle Core™ websites means that Entle is able to accomodate special use cases with other enterprise CMSes like Contentful, as well as direct integrations into other sources of content.

Netlify CMS

Read more:
How the Mandela Rhodes Foundation lets alumni edit their own website profiles, with a Graduway integration

Download now

Entle Core™ websites let you manage website content and landing pages using the same CMS interface. Easily create new landing pages and A/B tests without coding — it's as just simple as updating a blog post. Once they are set up, landing pages' performance is tracked in your website's analytics.

Entle Core™ websites plug into your existing lead processing and CRM. With functions, Entle Core™ websites can reliably capture leads and pass them to your lead processing or CRM, like HubSpot or Salesforce. And because these functions are serverless, they automatically scale up to meet massive traffic spikes with ease, just like your website.

FAQs

Entle Core™ websites are built and deployed within minutes of a change. You are able to see a live log of changes so you know exactly when your change is live.

An Entle Core™ website's source code is version-controlled and stored in a private, secure GitHub repository. When you use Netlify CMS, Entle Core's™ default CMS, the website content is stored in the same version-controlled repository as the source code and you can use a GitHub account to log into the CMS. When you opt for a hosted CMS, such as Contentful, your website's content is stored there and pulled into the website via an API.

Entle Core's™ CI/CD pipeline runs on GitHub Actions. Apart from offering a performant, reliable platform for testing and deployment, GitHub Actions brings the added benefits of single sign-on with Netlify CMS, great visibility on changes going live, and easy rollbacks to previous changes.

While terms like “serverless” and “the JAMstack” may seem newfangled, they are in fact simply well-established technologies deployed in a fresh configuration. For example, AWS S3, Cloudfront, and Lambda, the serverless infrastructure used by Entle Core™ websites, are industry heavyweights with a reputation for reliability. To read more how Entle reduces risk with proven technologies, please read Entle's infrastructure whitepaper.

Download the whitepaper

Entle's default disaster recovery process gives your nominated technical contacts direct access to the website code and content (GitHub repository), which also gives you access to the CMS and CI/CD pipeline. Step-by-step disaster recovery instructions are easily accessed through the repository's README. In addition, Entle works with clients to move their domain DNS management to Cloudflare, so that the Entle team has access for maintenance and your internal team has direct access to manage your other domain services, and for emergency changes. Note that as part of the initial website strategy, Entle works with your team to tailor this disaster recovery process to your internal context and requirements.

It's important to note that actual website downtime events are extremely rare, because Entle Core™ websites are serverless and run on AWS S3, Cloudfront and Lambda. These services are scalable and reliable by design. Nevertheless, Entle has 24/7 availability monitoring in 1-minute increments, provided by the industry-standard tool Pingdom.

Software lock-in: With the exception of Entle Core's™ key proprietary components detailed below, websites built with Entle Core™ have a far smaller lock-in than competing alternatives. For example, with a WordPress website, you are locked into the CMS, the theme, the programming language (PHP) and database (MySQL/MariaDB), and any premium plugins that you use to optimise for speed, SEO, and more. Entle Core™ websites are decoupled by design, meaning that the website's structure and features are not locked into the CMS, i.e. you can decide to switch to a different CMS when your needs change. Furthermore, data can be pulled in from new APIs and microservices as you develop them, opening further doors for expansibility. While Entle Core™ does not support this, the decoupled architecture even makes it possible to switch to a completely different static site generator in a different language (e.g. Hugo, in Go).

Infrastructure lock-in: The services used by Entle Core™ websites — AWS S3, AWS Cloudfront, AWS Lambda, and Github — are publicly-available and widely supported.

The key propietary components of Entle Core™ are (i) its boilerplate and suite of build optimisations for Eleventy and (ii) its custom CI/CD pipeline. While it is certainly possible to extricate Entle Core's™ boilerplate and optimisations from your website to leave a 'vanilla' Eleventy site, this does mean you will lose all Entle Core's™ optimisations, making your website significantly slower, less accessible and SEO-friendly, and less reliable. Similarly, it is possible to replace Entle Core's™ CI/CD pipeline with your own, but your website will lose the benefit of Entle Core's™ test suite and deployment optimisations.

Compare your current setup to an Entle Core™ website

Request a free audit of your current website infrastructure and software to see how it would compare to that of an Entle Core™ website. If your company qualifies, Entle will schedule a call to get started.

Request free audit or send to a colleague