What every developer and user needs to know about trust, quality, and reliability on the marketplace.
When you browse the Rival marketplace, you'll notice that functions carry labels. Those labels aren't just decorative. They tell you exactly how a function has been reviewed, how it performs, and what level of reliability you can expect before you ever activate it.
This post breaks down what each classification means, how functions earn them, and what happens behind the scenes to keep things running smoothly.
The Four Classifications
Every function on Rival can carry one or more of the following classifications. Think of them as layers of trust, each one earned through a specific process.
Verified: The function has been automatically reviewed by Rival's systems. This check covers structure, documentation, and expected behavior. Think of it as the baseline quality pass.
Rival Verified: A step above Verified. A member of the Rival team has personally reviewed and validated this function for quality, reliability, and real-world performance.
CortexOne Accelerated: This function is optimized to run on the CortexOne processor. That means faster execution, smarter routing, and the most efficient use of compute resources.
Enterprise: This function meets enterprise-grade standards for reliability, security, and production deployment. These are functions built for or approved by enterprise customers.
Where You'll See These Labels
Classifications show up everywhere in the marketplace experience:
On each function card in browse and search results
On the function detail page, alongside the last review date and developer info
In marketplace filters, so you can narrow results by classification or operational status
In the checkout and activation flow, where any external dependencies are clearly disclosed before you activate
If a function depends on outside APIs, you will see a notice: "Depends on external APIs and may be impacted by third-party outages." No surprises.
Reliability Monitoring: What Runs in the Background
Classification is the starting point. Ongoing reliability is a continuous process. Here is what Rival monitors for every published function:
Runtime Monitoring
Execution failures
Latency spikes
Malformed outputs
Timeout rates
Test Harness (for functions with external dependencies)
Functions that connect to outside services run scheduled validation tests to confirm:
APIs are reachable
Credentials are still valid
Outputs match expected results
Dependencies are healthy
Dependency Attribution
When something goes wrong, Rival traces exactly where the failure originated:
The function's own logic
The Rival platform
A third-party service
An expired credential or schema change
Operational Status: The Live Health Signal
Separate from classification, every function has a live status that reflects its current health:
Active: Function is operating normally and can be utilized.
Unavailable: Execution has been disabled due to a detected failure. The developer has been notified and is working to resolve it.
What Happens When a Function Fails
Failures go through a clear, structured workflow so that developers and users are never left in the dark.
1. Detection
Monitoring or the test harness identifies abnormal failure patterns.
2. Internal Alert
Rival operations and support teams are notified immediately.
3. Developer Notification
The developer receives an email with error details and clear remediation steps.
4. Marketplace Status Update
The function's status updates in the marketplace so users see accurate information in real time.
5. Customer Notification
If you are actively using the function and your workflows are affected, you will receive an email and an in-platform notification.
6. Resolution and Reinstatement
Once the function passes reliability checks again, it is reinstated and you will be notified that it is back online.
The Bottom Line
Function classification on Rival is not a one-time stamp. It is a living signal backed by continuous monitoring, structured failure response, and transparent communication at every step.
Whether you are a developer publishing your first function or a user building a workflow that depends on several, you can rely on these labels to tell you the real story.
Questions? Visit our Discourse or reach out to the Rival support team at help@rival.io.