START Try & Buy

contact us



iSmartFrame works with redundancy levels that allow it to handle sudden traffic fluctuations and guarantees an SLA of 99.9% on all available resources (compute, storage, network).
The following picture illustrates our solution architecture:

Users access the site contents via a load balancer: the load balancer distributes the traffic among the proxy instances (the number of proxy instances will change dynamically in relation to site traffic).
In detail, an iSmartFrame node consists of a NGINX reverse proxy and a proprietary SEO engine. By default, the statics pages are managed by the proxy: any dynamic contents will be required on the content servers. In this case, the engine will apply any post-processing tasks on contents or JS/HTML code.
A series of fallback mechanisms have been studied in order to improve the platform availability. In case of network or systems issues, iSmartFrame infrastructure can cope with the following occurrences:

  • FAILURE OF ONE OF THE PROXY NODES: the load balancer is notified and automatically diverts all requests to the only working proxies;
  • ALL PROXY FAILURE: load balancer bypasses iSmartFrame infrastructure and redirects all requests to customer CMS servers;
  • ISMART FRAME ENGINE FAILURE ON A PROXY: if this happens, the balancer continues to query NGINX, which – as soon as a blocking error is detected on iSmartFrame Engine – first tries to redirect the requests on the iSmartFrame to the other server nodes. If these do not eventually respond, it sends requests directly to the end customer CMS servers.


iSmartFrame is activated like any CDN (Content Delivery Network) and it lies between your web servers and your visitors (users and Google), allowing the SEO optimisation engine to perform all necessary modifications to the HTML content , HTTP headers, and so on. For these reasons, customer IT effort is minimum.
Having been deployed across a variety of platforms and configurations, iSmartFrame is guaranteed to be robust and flexible.
Three different configurations are available, all fully supported.

Configuration A

Typical scenario in which iSmartFrame is able to interface directly with the CMS. In this case, the data sent by the CMS is “original” and is not managed by further process or caching.

Configuration B

In this case iSmartFrame doesn’t connect directly to the CMS but instead passes from another proxy that provides CDN services and potentially also firewall/DDoS protection..

Configuration C

Here, iSmartFrame does not act as an endpoint, as an additional proxy / firewall / CDN is placed in front of it. The configuration is fully supported: the only recommendation (not mandatory) is to disable any optimisations to http headers, resources, url, in order to leave iSmartFrame to do its job.


Speeding up without breaking a sweat

The key to the success of iSmartFrame is simplicity. In its application, management, and functionality.
iSmartFrame is a plug and play solution that can be activated in just 48 hours with just a few easy steps and without disrupting normal operations.
The technical input needed from the site owner is minimal, as well as being fast and easy to carry out: with constant help and guidance from the Aritmetika team. No interference with the site architecture or original software is needed either. 

The systems complies with the maximum safety standards (ISO 27001) and additionally complies with all GDPR requirements. 

iSmartFrame creates a cache copy that is constantly optimised for Google crawlers and users. The new cache copy talks to the original cache copy, which can be limited in performance and will no longer be the source interface for visitors and search engines.