CurNext
Support
Get help with CurNext products, the dashboard, devices, and integrations - starting with self-serve resources, then a clear path to the right human inbox.
CurNext is invite-only and, under internal policies, does not onboard product users under 18. If you cannot sign in, confirm you were invited to a project before opening a support ticket.
Start here
Most setup and how-to questions are answered faster in Docs and the Knowledge Base than by email.
Documentation
Site path, solutions, API, SDKs, firmware, security, and commercial scope.
OpenKnowledge Base
Ask CurNext Assistant about products, hosting, pricing model, and common site questions.
OpenDashboard
Sign in to manage projects, devices, alerts, and membership - invite required.
OpenAPI playground
Interactive OpenAPI docs for buyer integrations under api.curnext.app.
Open
What product support covers
Account & access
Invites, sign-in issues for existing members, role confusion, and project membership questions.
Dashboard & alerts
Readiness views, alert behaviour, exports, and day-to-day use of the web product.
Devices & firmware
Node assignment, connectivity symptoms, and firmware stage / apply outcomes - with site context.
API & SDKs
Key usage, endpoint errors, and SDK setup for licensed Professional integrations.
Human channels
Weekdays, typically within one business day. Include project name, device IDs if relevant, and what you already tried.
| Team | Use for | |
|---|---|---|
| Product support | [email protected] | Existing customers - product, devices, dashboard, API runtime issues |
| Sales | [email protected] | Quotes, new rollouts, volume, commercial scope, Pricing follow-up |
| Security | [email protected] | Vulnerability disclosure and security incidents only |
| Legal / DPA | [email protected] | Data Processing Agreement and privacy counsel requests |
Before you write
- Project or organisation name as shown in the dashboard
- Your login email (must already be invited for product issues)
- Approximate time of the issue (timezone)
- Screenshots or exact error text where useful
- Device / node IDs for field hardware problems
- Whether the issue is reproducible, and steps you already took
Route correctly
Not a customer yet?
Use Pricing to estimate and request a quote, or Contact for company questions. Support is for active product use.
Open PricingGeneral company topics
Partnerships, press, and non-product inquiries go through Contact or [email protected].
Open ContactSecurity reports
Do not send vulnerability details to support@. Use coordinated disclosure at [email protected].
Security architecture