Render is growing quickly, so we launched a revamped Careers page that describes who we are, how we work, and the benefits of working at Render (and of course, our open roles).
August also included a lot of behind-the-scenes work to improve reliability: more observability, alerts, and automation. While reliability work isn't often visible, we will continue to invest in it because we think of it as a core part of UX.
Improvements and Fixes
- One-off jobs are now generally available.
- Logged in users can now change their password under Account Settings.
- We added a new message to indicate when a deploy is waiting for a successful health check, or when it fails the health check.
- Updated messaging for server health events: Server failedis nowServer unhealthy, andServer back upis nowServer healthy.
- The Server unhealthyevent now includes more context on the failure.
- Removed duplicate notifications from failed Log Streams connections to syslog endpoints.
- Increased PostgreSQL connection limits for the Pro Plus plan.
- Bumped default Go version in the build image for Static Sites to 1.17.
- WebSocket connections to your app will now use httpsfor the value ofX-Forwarded-Protoincreasing compatibility with application servers that do not recognizewss.
- Servers with disks now support user-schedulable maintenance windows.
- Cron jobs will use standard Render plans with varying CPU and memory effective October 1, 2021.
Jobs in Early Access
You can now create a Job to run a specific task to completion, or run many such tasks in parallel with different arguments. Please email email@example.com to get access to Jobs.
Improvements and Fixes
- PostgreSQL 12 & 13 are now generally available. New databases will use PostgreSQL 13 by default.
- You can now get information on Render users and teams through our (early access) REST API.
- All native environments now include postgresql-client.
- PostgreSQL Read Replicas now use the same IP access control settings as the primary database.
- Previously, not specifying a service plan in render.yamlcould revert it to the default. We fixed this behavior to only change the plan if it is specified inrender.yaml.
- Fixed an issue where Cron Job runs were being canceled if they ran beyond their next scheduled time.
PostgreSQL versions 12 & 13 in Early Access
You can now create PostgreSQL databases with major versions
13. Please email firstname.lastname@example.org to join the early access program.
Both versions include multiple performance and functionality improvements.
With PostgreSQL 13, you can also control your extensions with standard
Autoscaling with YAML
You can now manage autoscaling with
If you have a lot of services or your services require a lot of options, it can be helpful to define your Render infrastructure (services, databases, and environment groups) as code in a render.yaml file. Check out the docs to get started with autoscaling for your YAML services.
Zulip One-Click Deploy
You can now deploy Zulip on Render with a single click. Zulip is an open source real-time chat application like Slack, but with an email-like threading model. This model allows you to catch up on important conversations while ignoring others.
Zulip’s features include:
- Highly configurable notifications.
- Keyboard shortcuts.
- Mobile and desktop apps.
- Integrations with Trac, Nagios, Github, and more.
- Restful API with Python bindings.
Check out the docs to deploy Zulip to Render.
Improvements and Fixes
- If you use Render teams, we will now automatically switch to the correct context when you click on the link to a service.
- You can now click and drag to zoom into metrics.
- You can now view logs for managed PostgreSQL databases. These logs are also available in Log Streams. If your database was created before 2021-06-29, you will need to email email@example.com to enable logs for it.
- Log Streams now support Logtail and Datadog.
- We now support adding authentication tokens to Log Streams (docs).
- You can now filter your list of custom domains through our (early access) REST API.
- All native environments now include zipandunzip.
- Trial users can now create more than two static sites without adding a credit card.
- Going forward we will display a dashboard notification when the Render Terms of Service change.
- We've made it easier to roll back to a previous deploy by adding a button to each deploy in the Events tab.
Welcome to Render's May 2021 changelog! Going forward we will keep you updated on all the features, bug fixes, and improvements we're working on by publishing this document once a month. We hope it's useful as you grow your applications and businesses on Render; do send us suggestions for things you'd like us to include here going forward.
You can now automatically scale your services up and down based on target CPU and memory utilization.
Many services handle variable load: you might see regular increases in usage during the day, or a surge after launching a new feature. Autoscaling makes it possible to keep your services scaled to your needs without manual configuration. Check out the docs to get started.
You can now add read replicas to your Render PostgreSQL databases.
Read replicas reduce load on your primary database and make one-off queries safer. They are also a great option for data analysis tools that do not need to write to your primary database, or for running computationally expensive data analysis without impacting the performance of you primary instance. Read replicas are available on Standard database plans and above. Check out the docs to get started.
- You can now view additional database metrics for storage, active connections, and replication lag (if read replicas are enabled). For Standard database plans and above, you can select a time range to view database metrics.
- You can now trigger a database backup manually, and view backups in progress (docs).
- Trial users can now use Render disks up to 1 GB without adding a credit card.
- All environments now include magic-wormhole to transfer files to and from Render Disks using the web shell.
- We are rolling out dashboard notifications in the form of toasts. New users will see them first after email confirmation.
- You can now skip an auto-deploy by including a skip phrase in the commit message.
- You can now zoom into CPU and memory graphs on the dashboard.
- You can now manage your custom domains with Render's REST API. This functionality is stable, but is in early access while we build out other API endpoints; please email firstname.lastname@example.org to get access.
Fixes and Improvements
- We've improved the reliability, security, and performance for our Frankfurt infrastructure by increasing capacity, upgrading infrastructure components, and implementing encryption-at-rest for control plane data.
- We also published a detailed root cause analysis document for the May 6th incident affecting Frankfurt services. You can view it on the May 6th incident status page.
- We've hardened our SSL certificate renewal infrastructure to prevent certificates from expiring in a few specific cases.
- Docker image builds now use buildkit v0.8.2 (previously v0.7.2).
- Manually clearing the cache for static sites will now reliably remove all cached artifacts.
- We've improved error messages related to GitHub connection issues.
- We've added more compute capacity to power our (early access) REST API endpoints. This will make API calls faster and more reliable.
- We've made it easier to fix errors during service creation by automatically scrolling to the invalid field(s) in the dashboard.
- We've made it easier to read the the billing table when using screen readers.
- Fixed an issue where databases in an error state displayed an internal server error in the dashboard. These databases are now displayed with an unknown status.
- Fixed an issue where some database backups on Starter plans were failing.
- Fixed an issue where we displayed the incorrect due date on invoices.
- Fixed an issue where we incorrectly displayed services when an error occurred.
- Fixed an issue where we failed to resume suspended services in Frankfurt after users updated their payment information.
- We have disabled Render Addons. We used Manifold to provision Addons behind the scenes. Unfortunately, Manifold shut down operations in May 2021. All existing users should have already migrated their Render Addons using our migration docs.
Feature update! You can now create multiple environments from the same YAML through your Render dashboard. https://render.com/docs/infrastructure-as-code#creating-multiple-environments
As our user base has grown, we've approached the limits of Slack as a Q&A and help forum. We will be transitioning to a real forum for most interactions that don't involve emailing email@example.com, and you can get early access to it today by signing up at https://community.render.com.
Why you should use the forum instead of Slack:
- Your messages won't get lost in the barrage of Slack conversations: like with the Slack community, Render engineers will monitor and respond to posts in the community forum.
- It's a lot easier to have asynchronous conversations on a post vs. on a Slack thread, and even easier if you have multiple ongoing conversations with Render.
- You will get notified via email or an optional desktop notification when someone responds to a post. No need to keep checking Slack for a response.
- There are no history limits, so all questions will always be available and searchable.
- You can get alerted to new topics weekly/daily, just like with https://feedback.render.com.
- You can still have DMs with Render engineers in the community forum.
We'd love for you to try it out today! https://community.render.com
Automatic preview environments are in GA!
Automatic preview environments enable you to generate a complete replica of your production infrastructure for every pull request in your GitHub/GitLab repositories.
Test with precision and confidence, share upcoming and proposed changes with product and marketing, create sandboxes for sales demos, and reproduce user issues in a live production-like environment.
Learn more: https://render.com/docs/preview-environments
We've revamped Render's global load balancing code to be much more resilient to traffic spikes and DDoS attacks.
You can now suspend and resume databases from the dashboard.
To suspend a database use the Suspend Database button located below the Access Control section.
Suspended Databases can be resumed at any time using the Resume Database button.