Skip to content
FOVEUS PRIVATE BETA

Investigate the execution behind the failure.

Foveus is inviting a small number of .NET backend teams to test execution-first production investigation. Search by business context, open the relevant execution, and inspect the requests, logs, issues, and outcome evidence behind what happened.

Request private beta access Read the documentation

Access is currently invite-only.

Who the beta is for

Built for .NET teams investigating real production failures.

The private beta is intended for backend teams whose investigation often starts with a customer complaint, transaction reference, failed request, or recurring issue.

ASP.NET Core APIs
Multiple internal .NET services
Outbound calls to payment, identity, messaging, or other providers
Customer complaints containing an order, transaction, customer, or provider reference
Logs distributed across several services
Recurring production issues that take too long to reconstruct
HTTP-success responses that still produce failed business outcomes
What teams can test today

Current beta capabilities for API-first investigation.

Foveus is strongest today when the investigation starts from an API execution and needs to reach the requests, logs, linked services, issues, and outcome evidence around it.

Execution timelines

Inspect an incoming API request, its outbound calls, related downstream requests, logs, context, and resulting outcome in one investigation.

Business-context search

Find executions using indexed safe context such as a transaction ID, customer ID, order ID, or provider reference.

Cross-service evidence

Follow related incoming and outbound requests across instrumented .NET services instead of reconstructing the chain manually.

Logs in execution context

Inspect logs in the context of the execution that produced them rather than as isolated lines pulled from separate tools.

Issues and alerts

See recurring failure patterns grouped into issues, with alerts linked back to affected executions and their evidence.

Lightweight .NET setup

Install the Foveus SDK, add your API key, and send initial telemetry without deploying a separate agent.

What participation involves

What we ask from private-beta teams

The beta is a working relationship, not only early product access. We want teams that can try Foveus on real investigation paths and tell us where the evidence flow still breaks down.

Instrument one or two suitable .NET services

Attend a short onboarding session

Use Foveus during real development or production investigations

Report confusing behaviour and missing evidence

Participate in occasional feedback conversations

Avoid sending credentials or unnecessary sensitive payloads

How access works

What happens after you request access

Private-beta requests are reviewed manually. Submitting the form does not promise approval, a response time, or an automatic invitation.

  1. 1

    Submit your request

    Tell us briefly about your team, .NET stack, and investigation challenges.

  2. 2

    We review the fit

    We are starting with a small number of teams whose systems match the current beta.

  3. 3

    Receive an invitation

    Approved participants receive an email invitation tied to their approved email address.

  4. 4

    Create your workspace

    Use the invitation to create your account and instrument your first service.

  5. 5

    Start testing

    Use Foveus during real investigation scenarios and tell us what worked, what was unclear, and what evidence was missing.

Access request

Request private beta access

Tell us enough to understand whether the current beta is a good fit.

For example: customer complaints with only a transaction ID, failed provider calls, logs spread across services, or HTTP 200 responses with failed business outcomes. Please describe the problem without including credentials, customer data, or sensitive production payloads.

0/1500

We review requests manually. Submitting this form does not create an account, workspace, or invitation automatically.

Beta request intake still requires a configured backend endpoint in this environment. The form validates fully and preserves the invite-only lifecycle, but a real request is only recorded after the backend intake is connected.

Before broader availability

Still intentionally small.

Foveus is being built with a small number of .NET teams before broader availability. The goal of the beta is not to collect as many signups as possible. It is to learn whether Foveus helps engineers move from a complaint, failure, or alert to the exact execution evidence they need.

Request private beta access Read the documentation