Available Today

Access and Security

• Single sign-on: Log in with your existing NASA identity. No new passwords to remember.
• Strong authentication: Secure your account with multi-factor authentication (like a PIV badge or code) and passwordless sign-in.
• External collaboration: Partners from universities or other agencies can get access. Their institutions can even connect their own login systems.
• Built-in access controls: Your workspace only accesses data that you and your project are allowed to see. You never have to manage security keys or secrets.
• Data encryption: Your data is fully encrypted both when it is stored and when it is moving across the network.
• Active firewall: A managed web application firewall filters every request to keep the platform secure.
• True user accounts: You get a unique username and personal file ownership, making file sharing work exactly as expected.
• External cloud access: Project admins can link external cloud roles. Your workspace inherits this access at startup, letting you easily read data from a mission or institution account.

Flexible Workspaces & Computing

• Instant access: Start a workspace on demand immediately—no support tickets or waiting required.
• Flexible sizing: Choose your exact compute power at startup: Standard (4 GB memory / 4 CPU), Large (8 GB / 4 CPU), Extra Large (16 GB / 4 CPU), or up to 64 GB / 8 CPU on demand.
• Pre-installed software: Jump right in with Earth science, Python, and AI tools already loaded. Advanced users can also bring their own custom container images (a packaged set of software).
• Distributed computing: Spread a single, massive analysis across multiple machines when you need more power.
• Background processing: Send long-running notebooks to process on their own. The job keeps running even if you close your browser, freeing up your active session.
• Auto-scaling capacity: The platform automatically adds and removes computing machines behind the scenes based on user demand.

Storing the science

• Your own space: Your own private storage where files are saved securely and are waiting for you when you return.
• Team space: A collaborative file system for your project team to store and share data, models, and results.
• Project object storage: Private, large-scale cloud storage for your project that you can access directly from your notebook.
• Integrated data browser: Browse and download files from your project storage—as well as from public AWS science datasets—directly inside JupyterLab.

Integrated AI Tools

• AI in the notebook: Chat with AI assistants and run agents directly inside JupyterLab, powered by various model providers.
• Targeted coding help: Ask the AI to write code, explain complex sections, or fix errors within a specific notebook or a single cell.
• Agents and a secure gateway: Run AI agents on the platform through a single, trusted entry point. For safety, some workflows require human approval before taking action.
• The AI Registry in JupyterLab: Access a hub of NASA-validated AI building blocks—including MCP servers, skills, agents, models, prompts, and harnesses. Use the AgentRegistry panel to search, deploy, and equip your AI assistant with these tools. (Currently rolling out to all projects; See the tool reference.
• Model endpoints on demand: Import and call your own custom models, or connect to managed models, directly from your notebook.

Working Together

• Real-Time Co-Editing: Edit the same notebooks and files at the exact same time as your teammates. Markers show who is online, and everything saves to your shared space.
• Easy Activation: Project admins can turn this feature on instantly in the RPAdmin console without contacting support.

See Working together on the same notebook.

Cost Visibility & Tracking

• Your Own Usage: View your personal compute/storage usage and remaining budget right inside JupyterLab.
• The Big Picture: Project admins can track the entire team's spending against the budget from the RPAdmin console.

The RPAdmin console — self-service for project admins

RPAdmin is the web console for the person who runs a project. Everything in this list is self-service: the project admin does it, with no ticket to the platform team.

• Track cost. Compute hours, compute cost, and storage cost for the project.
• Set and share out budgets. Give each member a spending limit. The platform blocks giving out more than the project holds. (The project's total is set by the platform team, after the funds reach the Science Cloud.)
• See platform usage. Who is using what, and how much.
• Manage members and roles. Add members, remove members, and promote a member to project admin.
• Turn on collaboration. The project-level switch described above.
• Cross-account AWS access. Register one of your own AWS roles, and the platform hands it to your notebooks at start-up. With it you can use any AWS service in your own account from the Research Platform — for example, start an HPC cluster there, or read a mission bucket. (HPC means high-performance computing: a large group of machines for heavy jobs.) No access keys are copied, and no secrets sit in a notebook.
• Audit trail. Every account, membership, and budget change, with who did it and what changed.

See RPAdmin — the admin console.

Coming

These are agreed and being worked on. No dates. They are listed in rough order of how far along they are.

In active development

• Faster start-up. Keep launch time short even when your home space grows large.
• One-click Hugging Face models. Deploy a public model with one click and call it from your notebook.
• Better "my usage" view. Usage and remaining budget shown on the launch screen as well.
• Roles in the AI Registry. Per-user and per-group permissions, instead of one level for everyone.

Planned next

• Scored AI tools. Every tool in the catalog scored for quality and safety, with history.
• Plain-language search. Find a model, agent, or tool by describing what you need.
• Budget stop at launch. Show a true remaining balance, stop new workspaces when the project's money is used up, and let a project admin choose whether a member who passes their own limit is blocked or may keep spending from the project's pool.
• Storage cost per person. See what each member's object storage costs.

Being explored

• Project-defined machine sizes. A project admin builds and maintains their own list of server types for their team, instead of everyone using one platform-wide list.
• GPU machines. A GPU is a chip that is fast for AI and image work.
• Session detail. Per-session CPU, memory, and storage detail, to understand a cost and size the next run better.
• Review before publish. A draft-and-approve step before an AI asset goes live in the catalog.
• More clouds in the data browser. Google Cloud and Microsoft Azure support.

Want the engineering detail?

The full catalog, with an identifier for every feature and its status, is the Product Roadmap. This page is the plain-language summary of Part I of that file.