We just made a number of improvements to help Core power users self-serve Paperspace resources. 

With this update, you can now create private networks, spin-up shared drives, and assign public IP addresses to any machines that you manage!

Self-serve private networks improvement 

First up, we're pleased to bring private networks to all Core users. When you create a private network, you create a shared resource pool for your team that is isolated from every other machine and customer on Paperspace.

Once you create a private network, you can add machines and drives to the network to share with team members.

Be sure to read the docs for more info!

Self-serve private storage improvement 

Next up, we've made it easy to share a drive among multiple Core machines. After you create a shared network, you can spin-up a shared drive and attach it to the network in a matter of seconds!

For more information on shared drives, check out the docs!

Self-serve public IPs improvement 

Finally, we've made it a lot easier to claim and assign public IP addresses! While previously it was possible to assign a machine to a public IP after the machine was created, we've now streamlined the process to make it more visible at the team level.

To claim a public IP, simply visit the Public IPs tab in the console and claim the address. (Note that Public IPs are region-specific.)

To assign the new public IP to a machine, all we need to do is use the Assign feature to select the machine we want to expose to the public web. That's all there is to it!

If you get stuck please read the docs to learn more or reach out to us with any questions. 

Bugfixes fix 

• We resolved a troublesome issue that resulted in erroneous invoices being sent to a small number of users
• We decreased errors related to over-provisioning on the Paperspace public cluster
• We improved the strategy for guaranteeing hot nodes and faster startup times on the Paperspace public cluster
• We fixed a number of small issues related to Windows 10 BYOL machines

We've released a number of improvements and bugfixes for Gradient!

Gradient Notebooks now autosave by default improvement

We've improved the autosave functionality of notebooks! Whereas before only .ipynb files would save automatically, we now provide autosave functionality for all filetypes within notebooks.

Notebooks running on free GPU instances can now be private on Pro or Growth subscriptions improvement 

If you're on the Gradient Pro or Growth plan, notebooks that run on Free GPU instances can now be made private.

PyTorch container updated to version 1.10, TensorFlow container updated to 2.6.0 

We've updated both PyTorch and TensorFlow default containers in Gradient Notebooks to their latest stable release versions. The new runtimes are now available in the Gradient console. 

Other improvements

• Gradient Deployments are now able to pull from models registered in Gradient
• Overall GPU capacity has increased after addressing an issue related to read-only filesystems used by Gradient Notebooks

Bugfixes

• We fixed a bug in the notebook create menu that sometimes caused the Workspace URL field not to update when selecting a new runtime
• We fixed a bug in notebooks that sometimes caused deleted files to linger in the file management pane
• We fixed a bug in notebooks that caused an empty file to be added to new directories
• We fixed a bug that sometimes generated duplicate and triplicate notifications when switching teams

Gradient Notebooks just received a substantial speed boost during startup and teardown! As a result, you should experience snappier notebook starts and stops.

Notebooks now start and stop much faster improvement 

We've streamlined the architecture behind Gradient Notebooks to enable this improvement.  

What you need to know 

You will now need to install dependencies each time you start a new session. 

We recommend that you import libraries and dependencies at the top of your notebook or within a separate requirements.txt file.

We've added RTX4000 and RTX5000 instances to CA1 and NY2 regions, as well as multi-GPU instances for Linux, and new low-cost CPU-only instances for Windows!

Introducing RTX4000 and RTX5000 announcement 

We're pleased to announce RTX4000 and RTX5000 instances are now generally available! 

These cards are based on NVIDIA's Turing microarchitecture and are more than 40% faster than their Pascal series counterparts.

Try RTX

Multi-GPU instances now available on Linux! announcement 

You can now access multi-GPU instances across all regions when selecting Linux as your OS!

P5000x2 instances start at $1.56/hr while P6000x2 instances start at $2.20/hr. 

Try multi-GPU

Low-cost Windows instances now available improvement 

We solidified CPU-only offerings for Windows instances and now provide C5 - C10 instances at an affordable hourly rate.

For just $0.08/hr you can run a full Core VM in the cloud!

Other Improvements

• We improved our backend error monitoring capabilities giving us substantially more insight into performance degradation and remediation
• We accelerated our equipment purchasing plan to provide new hardware faster to meet demand
• We re-wrote some business logic around storage capacity to be able to deliver much faster upgrades

We've added file uploads as well as a number of useful improvements and bugfixes to Gradient Notebooks.

File uploader arrives in Gradient Notebooks announcement 

You can now upload files directly from the Gradient Notebook IDE file manager. To use the uploader select Upload File from the sidebar. Upload progress is visible at the top of the sidebar and uploaded files are available for immediate use. 

Other Improvements

• We've added a prominent Start Instance button to stopped notebooks to make it easier to pick up where you left off when returning to a notebook
• We've increased the visibility of the Stop Instance button
• We now provide CPU, GPU, and RAM system metrics in the notebook footer
• We added a link to the Billing  view from the main menu which makes it easier to find account-related information

Bugfixes

• We fixed a visual bug that caused notebook file delete confirmations to render as a button rather than as a text block
• We fixed an issue where files within a notebook would sometimes not have syntax highlighting
• We made it more difficult to run a container that requires a GPU on a CPU instances
• We fixed a bug that was causing some users to accidentally create multiple notebooks
• We fixed a bug that occasionally caused some notebooks to get stuck in a saving state 

For more info on this release be sure to check out the blogpost. 

We've added improved file management functionality to the IDE!

Better file management in Notebooks improvement 

Now you can add files and folders directly from the IDE.

You can also download files using the file manager.

As more file management enhancements come to the IDE we recommend you swap over to JupyterLab if you need something like a terminal with root access.

Other Improvements

• We now send GPU utilization metrics to the status bar (bottom left) in the notebook IDE
• When creating a new notebook with a specified workspace, we now load a preview of the files in the IDE while the notebook initializes
• When you use the Share feature in a notebook, we now include in the link the specific file you are sharing

Bugfixes

• We fixed a bug that sometimes caused notebooks nested in folders to have an incorrect working directory which caused issues when using relative paths
• We fixed a bug that sometimes caused long cell outputs to degrade notebook performance
• We fixed a bug that caused some notebooks to restart after being manually stopped by the user
• We fixed a bug that occasionally prevented large notebooks from loading offline

This week we released a complete rewrite of Gradient Notebooks!

This is an important release for Gradient. Right away you'll notice that we've brought notebooks up to the new Paperspace design standards while taking big steps to bring simple and scalable ML infrastructure into the notebook itself.

In addition to the new compute instance selection menu, we've also integrated system metrics as part of a status bar and a new file browser which will soon unlock new capabilities around data management.

Last but not least, the notebook experience is now substantially more performant across the board -- from spin-up to teardown to rendering and executing cells. 

There's plenty more to unpack so head over to the blogpost to see what else has changed!

Last month we introduced a product selector to the console. 

Today we've launched a second phase of console redesign, adding product and team selectors to the top navigation bar and removing the sidebar entirely.

You can now find all entities that used to appear in the sidebar on the horizontal subheading bar.

We hope you enjoy the breathing room. 

Full blogpost here.

There's a new product selector in the console sidebar! 

That means that you can now clearly delineate your Core and Gradient workspaces and have greater confidence navigating the console.

(There's also a new Paperspace Team & Accounts view to better manage your personal and team account settings.)

Gradient metrics load faster Gradient 

There was an issue where Gradient metrics would take a while to load if the workload had been running for an extended period of time. The new metrics experience is blazing fast!

New desktop app Core 

A new desktop app (v10.0) was launched with a snappier login experience. 

Other improvements and fixes

• Upgrade button moved to the navigation bar to increase available screen real estate 
• An API Keys link was added to the user profile icon menu

We've released autoscaling for model serving and deployments.

To get more details on autoscaling we invite you to checkout the blogpost and read the docs!