Quick Start (SaaS)
Get your first case processed on nestfleet.dev in under 15 minutes.
1. Create your account
Go to nestfleet.dev/signup and create a free account. No credit card required for the Community tier.
2. Create your first product
After login you will be taken through the setup wizard. You need:
- Product name — a human-readable name for your software product.
- LLM provider + API key — Anthropic, OpenAI, Google, or Ollama. The key is encrypted at rest and never leaves your account.
- Timezone — used for SLA windows and scheduled digests.
3. Connect a signal source
Navigate to Settings → Channels and connect at least one inbound channel:
Configure an inbound webhook from Postmark, SendGrid, or any SMTP relay that supports webhook forwarding.
GitHub
Install the NestFleet GitHub App on your repository. Issues and PR events will flow in as cases.
Telegram
Provide a Telegram Bot token. Users can message the bot to submit support requests.
Webhook
POST JSON payloads to the generic webhook endpoint from any source.
4. Send a test signal
From Settings → Channels, click Send test signal on your connected channel. A synthetic case will appear in your queue within a few seconds with a triage result and confidence score.
5. Review your first case
Open the Queue view. Your test case will show:
- Severity badge (P0–P4) assigned by the triage agent
- Case type (bug, question, feature request, outage, …)
- Confidence score and reasoning trace
- Suggested routing (which queue / team lead)
- Known issue matches (if any exist in your knowledge base)
Next step: Add your product documentation to the knowledge base under Knowledge → Sources. The more context NestFleet has, the higher the auto-reply confidence and the better the known-issue matching.
What's included in the free tier
| Products | 1 active product |
| Outcome Units | 100 / month |
| Signal sources | Email, GitHub, Telegram, Webhook |
| AI triage | ✓ Included |
| Auto-reply | ✓ Included (requires confidence threshold) |
| Change requests | ✓ Included |
| Audit trail | ✓ Full history |
| Support | Community (GitHub Issues) |