SSR as a Service



under development now ... Please receive the launch news.

Ultra simple usage

  1. Set as a CNAME or CloudFront custom origin
  2. Done!

When going serverless, I do not want to think about HTML.

You can concentrate on the front end applications. Leaving SSR to Renderly eliminates unnecessary complexity from the application. You do not need to lock in for Renderly, and you can close Renderly if you do not need SSR.

Real-time SSR

SSR is done for each request. It does not require crawling or batch processing, so you can always get the latest results. It can be cached if necessary.

For all PWAs

All HTML + JavaScript applications are supported. In Renderly's internal high-speed browser, the Web Components is also rendered accurately.