Starter templates
Clone a complete example, configure your API key, and run a real backend workflow with RocketStack.
Next.js
Verify Stripe events, enqueue them through RocketStack, and process them asynchronously in a Function.
What it demonstrates
Next.js
Store CSV uploads, queue processing jobs, and parse files asynchronously in a Function.
What it demonstrates
Next.js
Run application actions once in the future or repeatedly with Scheduler, Cron, and Functions.
One-time
Recurring
What it demonstrates
Building one of these in a real application? Apply for the private alpha.
Step 1
Copy the Next.js project from the repository and install dependencies.
Step 2
Deploy the Function and create any Queue, Storage, Scheduler, or Cron resources the workflow needs.
Step 3
Configure server-side environment variables. Never expose credentials in the browser.
Step 4
Start the app locally, trigger the workflow, and inspect executions in the RocketStack console.
Templates use standard RocketStack APIs and SDKs. MCP can help adapt an example to your existing application, but templates are not one-click console deployments.
Set up RocketStack MCPEach template fits within the Free plan included monthly allowances when used for development and testing.
They are working reference implementations with clear extension points. Review authentication, idempotency, monitoring, and data retention before deploying to production.
No. Templates are runnable code examples. You create RocketStack resources through the console, APIs, SDKs, or MCP-enabled coding clients.
Yes. The workflow pages include examples for other frameworks. The templates focus on Next.js because it is a common starting point for web applications.
Yes. Templates are ordinary application code. Adapt payloads, validation, storage, and delivery targets to match your product requirements.
Yes, within the Free plan included monthly allowances. See the pricing page for detailed limits.
