- Deployment review
- Review a proposed single-node or cascade topology and identify configuration, dependency, and operational risks before validation.
- Configuration guidance
- Map a concrete media path to the documented services, limits, status surfaces, and configuration sections that own its behavior.
- Troubleshooting
- Work from a reproducible symptom, logs, status output, and topology evidence to separate product behavior from infrastructure or integration issues.
- Readiness assessment
- Examine a planned workload, its failure boundaries, observability, and unresolved risks before a production decision.
Support, with clear boundaries.
dispergo is private alpha software. Technical assistance may be available for selected evaluations and deployments when the operator guide is not enough. Each request is reviewed against its scope, the current product status, and available engineering time.
Where help can fit
How requests work
Email [email protected] with the use case, environment, expected timeline, and the question or blockage. The initial request is used to decide whether the work fits the current product and available capacity.
If the request is a fit, the next step is a separately scoped written proposal. No paid engagement begins until the scope, timing, access boundaries, and commercial terms have been agreed.
Current boundaries
Asynchronous first
Email is the primary channel. Calls may be scheduled when they help move a defined request forward.
By prior arrangement
Assistance is not an on-demand help desk. Availability and timing are confirmed for each engagement.
No service-level promise
24/7 support, emergency response, uptime commitments, and guaranteed response or resolution times are not currently offered.
Customer-run infrastructure
Third-party systems can be considered during diagnosis, but their operation and resolution remain outside the dispergo product boundary.
Start with context
A useful first message gives enough evidence to understand the request without requiring access to the deployment.
- dispergo version or commit
- deployment topology and relevant dependencies
- expected behavior and observed behavior
- reproduction steps, timestamps, and redacted logs
- requested timeline and any access constraints
Security reports
Suspected security vulnerabilities should be reported privately to [email protected]. A commercial support agreement is not required for security reporting.