Projects
Isolate teams, products, environments, and customer-facing queues.
RustGrid gives you projects, tickets, custom fields, webhooks, API keys, usage limits, and audit trails through clean APIs, so you can build workflow products without rebuilding the backend.
Gridkeeper turns the RustGrid logo into a moving system symbol: part gear, part grid, part workflow signal. It reinforces the backend promise: every actor, ticket, API key, webhook, and audit event belongs to one reliable workflow core.
Build ticketing, approval, operations, and AI-agent workflows without rebuilding the backend. RustGrid provides the durable primitives your product, agents, and systems coordinate around.
Isolate teams, products, environments, and customer-facing queues.
Durable work items with type, priority, status, comments, and activity.
Human-readable collaboration plus audit-ready history for every state change.
Shape workflow data without hardcoding a new backend model for each app.
Send lifecycle events into agents, CRMs, billing, Slack, and internal systems.
Give apps, services, and automations narrow programmatic access.
Plan-aware usage limits for tickets, requests, keys, projects, users, and webhooks.
Request IDs, history, and retention policies for operational accountability.
Service desks, ops consoles, approval inboxes, implementation queues, and support workflows.
AI workers need durable state, idempotency, project scope, and audit history when they act.
Webhooks, scoped API keys, and API-first coordination connect RustGrid to your stack.
The Launch Console personalizes this with your project key and newly created API key secret.
curl -X POST "https://app.rustgrid.com/api/v1/tickets" \
-H "Authorization: Bearer <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: first-ticket-001" \
-d '{
"project_key": "LAUNCH",
"title": "First RustGrid ticket",
"description": "Created through the API-native quickstart.",
"type": "task",
"priority": "medium"
}'
Service desks, issue trackers, and kanban boards are examples of products you can build on API-native tickets, custom fields, webhooks, scoped keys, usage limits, and audit trails.
Incidents, requests, SLA views, assignment groups, and customer-visible status.
create ticket
type: incident
fields: impact, urgency, cmdb_service
webhook: incident.escalated
Projects, labels, watchers, comments, attachments, releases, and engineering triage.
create ticket
project: mobile
labels: bug, regression
fields: sprint, severity, component
Simple columns for work intake, operations queues, fulfillment, and lightweight CRM flows.
move ticket
from: queued
to: doing
idempotency_key: move_039
RustGrid is not a template. It is the backend you keep when the prototype turns into a real product: tenant isolation, idempotency, optimistic concurrency with ETags, request IDs, webhooks, plan limits, and audit history.
Use these prompts with your LLM or app builder. They ask for the frontend while RustGrid supplies the workflow backend, API contract, auth, and event model.
Build a responsive service desk web app using RustGrid as the backend. Include an incident list, SLA priority filters, assignment groups, comments, attachments, custom fields for impact/urgency/service, webhook settings, and API key management. Use the RustGrid REST API for tickets, labels, watchers, comments, attachments, custom fields, and webhooks. Keep the UI focused on operators who need to resolve work quickly.
Start with Builder for new products, move to Scale when operational volume grows, or use Enterprise for annual contracts with custom limits and support.
| Plan | Free | Builder | Scale | Enterprise |
|---|---|---|---|---|
| Price | 0 €/month | 99 €/month | 899 €/month | Annual/custom |
| Projects | 2 | 10 | 100 | Custom limits |
| Users | 3 | 15 | 100 | Custom limits |
| Active API keys | 2 | 10 | 100 | Custom limits |
| Tickets | 100/month | 5,000/month | 100,000/month | Unlimited usage |
| API requests | 10,000/month | 250,000/month | 5,000,000/month | Unlimited usage |
| Webhook subscriptions | 1 | 10 | 100 | Custom limits |
| Webhook deliveries | 1,000/month | 50,000/month | 1,000,000/month | Custom limits |
| Storage | 1 GB | 50 GB | 1 TB | Custom limits |
| Custom fields | Not included | Included | Included | Included |
| Audit retention | 7 days | 30 days | 365 days | Custom retention |
| Support | Community access | Standard onboarding | Priority onboarding | Contract support |
RustGrid gives searchers and builders a direct path from the workflow they need to the API that powers it.
Build product-native ticket queues without adopting another full ticketing UI.
Add durable workflow state, fields, webhooks, and scoped credentials to custom tools.
Use ticketing primitives through APIs where Jira-style screens do not fit.
Use RustGrid as the backend for support, operations, customer success, and automation queues.
Give agents durable tasks, status, handoff, webhooks, and audit trails.
RustGrid is not a hosted Jira clone. It is API-native workflow infrastructure you can use to build Jira-style issue trackers, service desks, approval systems, operations consoles, and agent workflows with your own frontend.
Yes. Agents can create and update tickets through scoped API keys, use idempotency keys for safe retries, and leave auditable workflow history that humans and systems can inspect.
Yes. RustGrid supplies projects, tickets, custom fields, webhooks, API keys, usage limits, and audit trails through APIs. Your product owns the UI and business language.
Webhooks send workflow events such as ticket creation and updates to your systems, automation workers, data pipelines, notifications, or AI agents.
API keys provide scoped programmatic access for apps, scripts, partners, and agents. The console shows a key secret only once after creation, so store it in your own secret manager.
RustGrid returns clear API errors for plan or rate limits. The console and billing page show usage against tickets, requests, keys, projects, users, webhooks, storage, and audit retention where the API exposes those counters.
Yes. The Free plan includes 2 projects, 3 users, 2 active API keys, 100 tickets/month, 10,000 API requests/month, 1 webhook subscription, 1 GB of attachment storage, and 7-day audit retention.