May

Welcome to our changelog! 🚀

Stay updated on the latest changes and improvements in nullplatform.

---

✨ Insights into your organization

We’ve introduced the new Insights view—a central place to explore application activity and trends across your organization.

From deployment metrics to service usage, track key patterns and workflows in a single, consolidated view.

What you’ll find in Insights:

• DORA metrics to help you analyze deployment frequency, lead times, and success/failure rates.
• Application, scope, and build tracking to stay on top of development activity.
• Service visibility to understand usage, spot orphans, and monitor service health and activity.

👉 And this is just the beginning. If you're building your own insights or tracking additional metrics, let us know—we’d love to collaborate and explore how we can help.

✨ Introducing custom scopes

We’re thrilled to introduce custom scopes—a flexible way to craft your own scope implementation to deploy LLM agents, banking cores, mobile applications, static frontends, PL/SQL, or any technology you need. You can also use custom scopes to tailor your Kubernetes deployment at the micro level.

Key highlights:

• Seamless UI experience: Custom scopes behave just like traditional ones, with no extra learning curve for end users.
• Full feature compatibility: Use parameters, approvals, and policies just as with traditional scopes.
• Craft your own experience: Tailor creation and editing workflows to fit your specific requirements using our visual editor.
• Made for service crafters: as custom scopes and services share many concepts and standards, service crafters will be coding their custom scopes right away.

👉 Learn how to create and use custom scopes in our docs.

✨ Access to secret parameter values is now available​

A long-awaited feature is here! You can now access the content of secret parameter values—while maintaining precise control over who gets access and when.

To view secret parameters, go to Development > Parameters, select a parameter for more details, and click Show secret values.

Here’s how it works:

• Set up fine-grained approvals to validate each access request.

  

• Define policies to automate approval grants or denials based on your rules.

  

• And you can also rely on the SecOps role, which always retains access to secret values—when granted to the role.

👉 Learn more in our Parameters docs.

✨ Platform settings: approvals and policies

Take control of your workflows with a new UI for approvals and policies. View configurations and policies directly in the interface to ensure compliance and streamline governance.

You can now see in the UI:

• Approval actions: See which entities have approval actions and where they apply (by NRN).
• Action details: View type, status, and descriptions (e.g., “This action requires manual approval”).
• Policies: Review rules, such as:

Deployment must not have critical vulnerabilities:

{
  "build.metadata.security.critical": {
    "$lte": 0
  }
}

Coverage should be above 80% to allow deployments

{
  "build.metadata.coverage.percent": {
    "$gte": 80
  }
}

Go to Platform settings > Approvals > Configurations to see your organization's approval and policy setups.

👉 More info in our Approvals docs.

✨ Platform settings: improvements to channel creation

Last month we announced our new channel creation feature from the UI. This month, we’re enhancing it with advanced filter options.

What’s new:

• Select fields, operators, and values using dropdowns.
• Combine AND/OR conditions and group them as needed.
• Simplifies how notifications are filtered and sent to channels.

This greatly simplifies the way notifications are sent to a channel.

To get started, go to Platform settings > Channels and click + New channel, or edit an existing one.

👉 Check our Filters docs for usage examples.

Example: Setting filters for when an application is created successfully

✨ We're updating how services are deleted

We’ve changed how service deletion works to help you avoid orphaned infrastructure and unnecessary costs.

What’s new:

• If a service has a delete action, that action must be executed before deletion.
• Alternatively, deletion can be forced with a specific parameter (force=true).

Trying to delete a service without executing the delete action now results in an error unless the override is used.

Here's an example:

CLI

np link delete --id <LINK_ID> --force true

cURL

curl -X DELETE 'https://api.nullplatform.com/link/:id?force=true' -H 'Authorization: Bearer <token>'

👉 For more info, see our API reference docs.

✨ Compare services across environments

You can now compare service configurations across environments—like development, staging, and production—to catch and resolve discrepancies before they cause trouble.

How it works:

1. Select a source and target service to compare.
2. Get a structured diff showing what’s been added, removed, or changed.

The payload will look something like this:

{
  "diff": [
    {
      "operation": "replace",
      "path": "/attributes/endpoints/2/path",
      "source_value": "/api/v1/users",
      "target_value": "/api/v1/user"
    }
  ]
}

This feature helps you:

• Keep environments consistent
• Spot drift fast
• Confidently promote changes

👉 Learn how to compare services in our docs.

✨ Latest updates to our CLI

We’ve added several improvements to the nullplatform CLI for a smoother experience:

• New commands: manage users (np user) and providers (np provider and np category).
• Custom scopes workflow: Simplify scope definition with (np service workflow).
• Pagination support: Use offset and limit flags for list commands.
• Filtering scopes: Scope lists now support type and status filters (np scope list).
• Consistency updates: Replaced update commands with patch for entity updates.
• Deprecation notice: -specification commands (e.g., service-specification) will migrate to subcommands like np service specification. Both formats will work temporarily.

👉 See our CLI docs for more info.

✨ NewRelic logging support for AWS EC2

We now support NewRelic for logging in AWS EC2 environments.

How to set it up:

1. Go to Platform settings > Logging.
2. Click + New configuration and select the provider.
3. Fill in the required configuration details.
4. Click Create configuration to save your setup.

👉 For more info, see our Supported integrations docs.

✨ Adjust ingress manifest with object modifiers

You can now use object modifiers to adjust your ingress manifests with greater flexibility.

Key benefits:

• Dynamic configuration – Automatically adjust manifests to your context
• Reusable patterns – Define once, apply across environments
• Context-aware replacements – Inject runtime variables on the fly

---

Wishing you a fantastic month ahead – from the nullplatform team! ❤️