August 1, 2023


Here is the first changelog entry for Noop. From here on out, we will keep Noop users and other interested people up to date on product development here. The plan is to run these updates monthly. Published at the beginning of the month and covering the prior month of work.



Notifications give users the ability to receive email and in-app messages about problems with their Applications: Build, Deployment and Pipeline failures.

Individual users can enable Notifications at the Organization, Application or Environment level. The notification message itself is sent to users in-app and via email.

Every notification is associated with an Engagement center chat, so when you need support you can immediately message the Noop team.

External Proxy

The external proxy is a way to route traffic from an Endpoint to some external target (URL). It’s a way for developers to bring external applications under the same domain as their Noop apps.

It is how we’re starting the migration of the Noop Console app to Noop itself.

Noop on Noop

With the introduction of the external proxy feature outlined above, we’re now able to host the Noop homepage and the Console on the same domain (without subdomains).

By the way, we have a homepage! Also released this month.

Tier 1 Support

When things go wrong we are here. And we’re making it easier to let us know when things go wrong. Of course, this feature uses our Engagement Center. When you open any chat in the engagement center, you’re immediately promted to let us know if you’re experiencing a problem.


We simplified the user-facing identifiers for many Noop entities. Now, Pipeline, Builds, Deployments, etc. are represented by auto-increment numbers instead of random alpha-numeric values. For example: The forty-second build for a specific application can now be referred to as “Build #42”. This change makes it easier for humans to communicate about Noop platform concepts.


Of course we’re always improving the underlying system that supports the Applications running on Noop. To that end we have:

  • Improved cluster capacity management, increasing application service stability
  • Created an easy to update template for external system alarms. This includes signals from outside Noop such as user communications.
  • Improved system stability. Noop is protected against more edge condition failures and has a better ability to self-correct.
  • We improved system scaling process

And we’re continuing to hone the user experience:

  • Improved navigation and menu organization
  • Improved panel persistence across pages

And make updates to our core libraries:

  • Logic arithmetic operations support null arguments, defaults to 0, eliminating the need to check for null values before performing an operation.

And added docs for: