ShipAI.today gives agents everything they need to go from zero to launch, including auth, billing, admin, SEO, and AI workflows. All with full source code and a commercial license.
import Stripe from "stripe";
import { StripeApiError, getStripeClient } from "./client";
import type {
CheckoutSessionResult,
CreateCheckoutSessionParams,
} from "./types";
export async function createCheckoutSession(
params: CreateCheckoutSessionParams,
): Promise<CheckoutSessionResult> {
const stripe = getStripeClient();
const metadata = {
user_id: params.userId,
plan_id: params.planId,
...(params.metadata || {}),
};
try {
const sessionParams: Stripe.Checkout.SessionCreateParams = {
mode: "subscription",
line_items: [
{
price: params.priceId,
quantity: 1,
},
],
success_url: params.successUrl,
cancel_url: params.cancelUrl,
metadata,
subscription_data: {
metadata,
},
allow_promotion_codes: params.allowPromotionCodes ?? true,
billing_address_collection: "auto",
};
if (params.customerId) {
sessionParams.customer = params.customerId;
} else if (params.email) {
sessionParams.customer_email = params.email;
}
if (params.trialPeriodDays && params.trialPeriodDays > 0) {
sessionParams.subscription_data!.trial_period_days =
params.trialPeriodDays;
}
const session = await stripe.checkout.sessions.create(sessionParams);
return {
sessionId: session.id,
url: session.url,
};
} catch (error) {
if (error instanceof Stripe.errors.StripeError) {
throw StripeApiError.fromStripeError(error);
}
throw error;
}
}
export async function getCheckoutSession(
sessionId: string,
): Promise<Stripe.Checkout.Session> {
const stripe = getStripeClient();
try {
return await stripe.checkout.sessions.retrieve(sessionId, {
expand: ["subscription", "customer", "line_items"],
});
} catch (error) {
if (error instanceof Stripe.errors.StripeError) {
throw StripeApiError.fromStripeError(error);
}
throw error;
}
}
export async function expireCheckoutSession(
sessionId: string,
): Promise<Stripe.Checkout.Session> {
const stripe = getStripeClient();
try {
return await stripe.checkout.sessions.expire(sessionId);
} catch (error) {
if (error instanceof Stripe.errors.StripeError) {
throw StripeApiError.fromStripeError(error);
}
throw error;
}
}Every layer from runtime to payments is configured, typed, and glued together — no scaffold work required.
Marketing site, core app, and docs — all production code in the purchase. Not locked behind a managed platform or a monthly fee.
Landing + conversion flow
Core app surface
Feature and documentation depth
ShipAI bundles the hard parts into one production baseline: AI handlers, auth, payments, ops, and SEO foundations.
AI handlers · Deep-research flow · Qdrant vector memory · BullMQ background jobs · OpenTelemetry tracing.
Magic links · Phone OTP · OAuth (Google, GitHub, Discord) · Guest users · Protected routes · Session management — all wired end to end.
Stripe checkout · Subscription portal · Webhooks · One-time payments · Usage metering · Plan enforcement on every route.
Programmatic SEO routes · Dynamic sitemap · Robots.txt · Canonical helpers · JSON-LD structured data · Metadata utilities pre-wired.
The runtime, database, AI, infrastructure, and frontend layers are chosen to ship fast and stay maintainable once users arrive.
Explore the stack
Bun · Next.js 16 · TypeScript 5.5
PostgreSQL 17 · Drizzle ORM · Redis 7.4
Vercel AI SDK v6 · Groq + OpenAI · Qdrant · Neo4j 5.26
Docker · MinIO/S3 · BullMQ · Tailwind v4 · Shadcn UI
The license, docs, AI-friendly structure, and deployment model are tuned for builders who want control over code, margins, and roadmap.
See full preview
One-time payment with full code, commercial rights, and lifetime updates.
Runs locally with Docker Compose and deploys without forced managed services.
AGENTS.md, structured docs, and llms.txt help Cursor, Claude, and Copilot stay useful.
Programmatic pages, metadata helpers, sitemap generation, and JSON-LD are already in place.
Speed for a reason: install, copy `.env`, boot Docker, migrate, seed, and start from a working baseline.
Local infrastructure is part of the path, not a weekend integration task.
You start from a running app instead of a folder full of placeholders.
Magic links, OAuth, phone OTP, sessions, protected routes, and role-aware access patterns are part of the baseline.
User and admin access are separated from the start.
The first login flow does not require custom plumbing.
Stripe checkout, billing portal, webhooks, one-time payments, subscriptions, and plan enforcement are already part of the product model.
Usage limits are designed into the app, not bolted on after launch.
Common payment edge cases are handled closer to the source.
Includes AI handlers, deep research flows, multi-provider routing, and usage tracking around real workloads.
Standard chat and more complex research can share one system.
Model-provider swaps do not force a rewrite of the product logic.
Admin views, structured logs, tracing, metrics export, and Telegram alerts cover the parts teams usually postpone until production hurts.
You can inspect failures and usage without building an internal tool first.
Observability exists before the first serious incident.
Shipped with 60+ components for forms, dialogs, navigation, tables, charts, badges, and other app surfaces.
Useful for product screens, not just hero sections and pricing blocks.
A larger component base shortens the second month of work too.
Welcome, magic-link, email verification, and OTP delivery templates are already part of the baseline instead of being left as plain text stubs.
Onboarding emails are ready to rebrand rather than invent.
Auth-related email flows feel consistent with the rest of the product.
Transcription, indexing, cleanup, and other background work follow an existing worker pattern instead of being forced into request-time handlers.
Slow or heavy tasks stop leaking into the main app flow.
Adding a custom processor follows a path that already exists.
7 languages with externalized copy that makes adding more locales realistic later.
You avoid hunting text across random components once growth starts.
Marketing and app copy can evolve without breaking translation hygiene.
Get the landing implementation itself: sections, layout, styles, and motion, ready to clone and rebrand.
Exact landing source included
You get the same landing implementation, ready to clone and rebrand.
Production sections already built
Hero, features, testimonials, and the rest of the pages as production components.
Conversion blocks are ready
Pricing, CTA flows, and the core sales sections are already in place so you can adapt faster.
Edit and launch faster
Swap branding, adjust copy, and publish a polished marketing site without rebuilding the landing system from scratch.
Get practical help during setup and first launch so blockers do not slow down the initial release.
Direct access to the author
Ask implementation questions and get practical guidance.
9-5 Discord support window
Consistent support hours help you stay unblocked during setup and launch.
Setup and launch guidance
Get hands-on direction for environment setup, implementation decisions, and early release steps.
Momentum during the first release
Use the support channel to validate decisions quickly and keep the initial launch moving instead of stalling on edge cases.
This boilerplate is organized for humans and autonomous coding agents. Repository-level guidance in AGENTS.md combines with modular SKILL.md packages so tools can discover intent quickly, load deeper instructions only when needed, and execute project conventions consistently across Claude Code, Codex, OpenCode, and GitHub Copilot.
Everything In One Kit
Ship with a complete SEO foundation already wired in — no retrofitting required:
AI SaaS Boilerplate — Next.js
https://shipai.today
Difficulty
28
Position
4/10
Impressions
9.2K
Trend
+31%
Intent
Commercial
CPC
$2.40
Index
Confirmed
CPC
$0.00
ShipAI.today ships a production-ready Telegram bot setup out of the box: webhook route, DMs and group mentions, slash commands, file attachments, and billing-aware upgrade flows.
Slash Commands
/upgrade
Get a secure payment link to upgrade your plan
/plan
Show your current subscription and renewal period
/usage
Display usage vs limits: chats, searches, storage
Bot Capabilities
DM & Group support
Responds to DMs directly; groups on @mention
Attachment processing
Upload files, images - injected into AI context
Billing integration
Signed upgrade links tied to your Telegram identity
Payment success notify
Bot sends confirmation when checkout completes
Slash Commands
Get a secure payment link to upgrade your plan
Show your current subscription and renewal period
Display usage vs limits: chats, searches, storage
Architecture note
POST /api/webhooks/telegram
The bot uses the same product context and billing-aware flows instead of becoming a separate disconnected tool.
Bot Capabilities
DM & Group support
Responds to DMs directly; groups on @mention
Attachment processing
Upload files, images - injected into AI context
Billing integration
Signed upgrade links tied to your Telegram identity
Payment success notify
Bot sends confirmation when checkout completes
Same AI, any channel
Telegram bot reuses buildChatStream - identical AI power via webhook, no separate pipeline.
Identity-mapped users
Telegram accounts map to internal users via DB-backed providerId - full billing context preserved.
From the /cases page — builders who shipped sooner using the stack. Quoted directly, not written by a marketer.
“I've killed three side projects at the infrastructure stage. Not because I couldn't build it — because by the time everything was wired up, I'd lost the will. This time I had a working product in front of users on day two. That's what changed.”
Marcus Chen
Founder · Taska
“We're three people. We don't have a dedicated backend engineer and we probably never will at this stage. We needed something we could all understand, extend, and not babysit. ShipAI is the first foundation where that's actually been true.”
Priya Ramachandran
Co-Founder & CTO · Clio Analytics
“We'd been quoting customers for months before we had anything to show. The first time I demoed a live product, the conversation changed completely. SupportLayer went from a pitch deck to something real in about two weeks.”
Daniel Hoffmann
Technical Founder · SupportLayer
“I've been a designer my whole career. I started taking on full-stack client work two years ago and it's been a constant anxiety. This is the first codebase I've worked in where I genuinely feel like I know what's going on. I'm not just hoping things work.”
Ana Whitfield
Designer-Developer · Forma Studio
“I had six weeks to build something investors would believe in. I'd already spent three months on infrastructure that wasn't the product. ShipAI was the reset I needed — it let me spend those six weeks on the parts only I could build.”
Jerome Okafor
Founder & ML Engineer · Contextual AI
“I spent the first two years of Patch Labs losing Monday mornings to my own dev environment. It sounds trivial but it compounds. Getting that time back didn't just change my velocity — it changed my relationship with the project.”
Sofia Lindqvist
Indie Developer · Patch Labs
“We've shipped seventeen client products. The first two weeks of every engagement used to look the same: auth, billing setup, SEO plumbing, deploy pipeline. Now we skip all of it and go straight to the product. Clients don't notice — they just get their thing faster.”
Ryan Castellano
Technical Director · Meridian Studio
“I had three pricing tiers, per-user AI credit metering, and a Stripe customer portal live before I wrote a single line of product code. That kind of infrastructure usually takes me two weeks. Doing it in a day meant I could spend the rest of the sprint on the actual editor — the thing users pay for.”
Leila Mansouri
Solo Founder · DraftIQ
“Our first enterprise prospect asked for a security review before signing. I thought that would take weeks to prepare for. We passed in a week with no critical findings. That contract was the difference between a side project and a real company.”
Tobias Wolf
Bootstrap Founder · VaultPass
“We were shipping fast but breaking things just as fast. Every new feature felt like a gamble. Migrating to ShipAI was uncomfortable — it took a sprint just to move — but after that the codebase started feeling predictable again. That's worth a lot when you're a team of two.”
Nina Kozlova
Co-Founder · ReviewKit
“I build almost everything with AI assistance now. The difference isn't the model — it's whether the codebase gives the AI enough context to generate something useful. ShipAI's structure does that from day one. My output is faster and the code doesn't need nearly as much cleanup.”
Alex Oduya
Indie Maker · BuildStack
“I was running MetricLoop out of a spreadsheet and Stripe's dashboard for the first four months. When I started talking to investors, I realized that story didn't hold. Getting actual operational tooling in front of them changed the dynamic immediately.”
Camille Dupont
Solo Founder · MetricLoop
Straightforward answers about what ships, how the license works, who it's for, and what happens right after checkout.
Most boilerplates solve the easy parts — auth, a Stripe checkout, a landing page — and leave the hard parts to you. The hard parts are the AI orchestration layer, background jobs, observability, admin visibility, and SEO. ShipAI includes all of it: 11 modular AI handlers, deep-research pipelines, BullMQ workers, OpenTelemetry tracing, a full admin dashboard, and programmatic SEO foundations. The gap shows up fast: auth and Stripe take a week to wire up yourself; a production AI stack with memory, streaming, and job queues takes months. ShipAI compresses that to one git clone.
Open source boilerplates are great until they get good — then companies sponsor them and you end up paying anyway. Paid ones have been on the market for years without offering anything truly innovative. ShipAI is built from 10+ years of hands-on development experience, requires zero forced external dependencies, runs fully locally, and can be deployed to a cheap VPS without relying on any third-party SaaS.
Full source code, commercial license, auth and billing, 11 AI handlers, admin panel, 60+ UI components, programmatic SEO, Docker dev environment, docs, and private Discord support. One payment, no recurring fees, no tiers.
Yes. You bring your own keys for AI providers. The stack runs on Docker Compose locally and deploys to any container-friendly environment — no forced managed services.
Unlimited SaaS products — for yourself or clients — with no attribution or royalties. You cannot resell or redistribute the starter kit source itself.
Yes. The /preview page shows components and landing sections. The /docs and /features and demo pages are fully public. There is also a 14-day refund policy if it is not the right fit.
You should know Next.js and TypeScript basics. Beyond that, ShipAI is straightforward to extend — including with AI coding tools. The repo ships with an AGENTS.md and structured docs built for vibe-coding workflows.
One checkout, then auth, billing, AI, admin, and SEO are yours to shape into the product.
Lifetime updates included. No subscriptions.
trusted by 198 builders
License & Ownership
AI System
Memory & RAG
Auth & Billing
Jobs & Storage
Admin & Observability
SEO & UI
Telegram Bot
Infrastructure & DX
BullMQ background jobs deep-dive
3d agov2.5.0 Bun + Next.js 16 upgrade
10d agoStripe webhooks setup guide posted
17d agoTelegram billing + slash commands
24d ago
