Mikita Aliaksandrovich

We launch a feature here on Thursday, and the landing page section for it is the one new users keep bringing up on calls and in replies, more than the hero, more than pricing.

It is a simple block. One sentence: see the change before it ships. One picture of a working copy of your site with the change on it, and two buttons: approve, or send it back.

I think it works because it answers the question people actually have about any tool that writes code for them: what if it gets it wrong? The answer is not trust us , it is look at it first . The other sections explain what it does. This one removes the fear.

Curious what the equivalent section is on your landing page: the one that answers the fear rather than describing the feature. And for those who have run the test, did it convert better than the feature description?

Hi everyone,

In April we launched Ovren here and finished #4 Product of the Day. The question we heard most since: "The change is ready, but how do I know it looks right before it goes live?"

On October 22 we're launching Live Preview.

Describe the change you want in plain words, like "add a customer reviews section under the banner." Ovren makes the change on a safe copy of your website or app and shows you the result: your real page, with the change on it. Click around it like a visitor would. If it looks right, approve it and your team publishes it. If not, send it back with a note.

We teamed up with @GoogleCloud for a Cloud Run Hackathon October 14th!

To kick things off, we're celebrating on the leaderboard so you can meet the people behind Cloud Run.