GetShipKit Documentation

GetShipKit provides a production-ready foundation for your SaaS project with built-in authentication, payments, and database integration. Our enterprise-grade starter kit helps developers launch modern SaaS applications in days instead of months by eliminating boilerplate setup and infrastructure challenges.

Prerequisites

• Node.js (v18+) and a package manager (npm, yarn, or pnpm)
• Git for version control and a modern code editor (VSCode recommended with TypeScript extensions)
• Service accounts from our technology partners:
  • Supabase account for PostgreSQL database
  • Clerk account for authentication
  • Polar.sh account for payment processing
  • Vercel account for deployment (optional: any Node-capable platform works)

What's Included

• Authentication & User Management: Secure authentication with social logins, multi-factor authentication, and complete user profile management via Clerk
• Database & Backend: Supabase PostgreSQL with pre-configured schema, row-level security, and optimized indexes
• Billing Solutions: Subscription plans, one-time payments, and usage-based billing via Polar.sh with webhooks integration
• Modern UI Components: Responsive dashboard with dark/light modes, accessibility compliance, and Tailwind CSS styling
• DevOps Ready: Optimized for CI/CD pipelines with containerization support

Follow these steps to get your SaaS application up and running quickly. The entire process takes approximately 3 minutes.

GetShipKit leverages Clerk for full-stack authentication with social logins, JWT management, and secure session handling. This drop-in solution handles user sign-up, sign-in, profile management, and authorization.

# .env.local
NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_test_****
CLERK_SECRET_KEY=sk_test_****

1
2
3
4
5
import { authMiddleware } from "@clerk/nextjs";

export default authMiddleware({
  publicRoutes: ["/"],
});

Supabase PostgreSQL powers the database layer with robust relational data management, real-time subscriptions, and built-in Row Level Security (RLS) policies for granular access control.

NEXT_PUBLIC_SUPABASE_URL=https://[project].supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=anon-key
SUPABASE_SERVICE_ROLE_KEY=service-key

Row Level Security in Action

Supabase uses PostgreSQL Row Level Security to ensure users can only access their own data. The schema creates appropriate policies that restrict data access at the database level.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
-- Create tables
CREATE TABLE IF NOT EXISTS profiles (
  id UUID PRIMARY KEY REFERENCES auth.users(id) ON DELETE CASCADE,
  email TEXT UNIQUE NOT NULL,
  full_name TEXT,
  avatar_url TEXT,
  created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL,
  updated_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() NOT NULL
);

-- Row Level Security Policies
ALTER TABLE profiles ENABLE ROW LEVEL SECURITY;

-- Policy: Users can read their own profile
CREATE POLICY "Users can read own profile"
  ON profiles
  FOR SELECT
  USING (auth.uid() = id);

-- Policy: Users can update their own profile
CREATE POLICY "Users can update own profile"
  ON profiles
  FOR UPDATE
  USING (auth.uid() = id);

Subscriptions and one-time payments are handled via Polar.sh, a modern payment platform that supports multiple pricing models, global payment methods, and automated subscription lifecycle management.

GetShipKit is designed to be deployed on any modern hosting platform. We recommend Vercel, Netlify, or any Node.js-capable platform.

# Build the Docker image
docker build -t getshipkit .

# Run the container
docker run -p 3000:3000 getshipkit

GetShipKit follows Cursor's premium design rule-sets ensuring accessibility and consistency. The project includes Cursor rules files that help create a perfect UI and UX when working in the Cursor app.

The repository includes legal-page-prompts.md with AI prompts to generate legal pages such as Terms of Service and Privacy Policy.

Always have any generated legal text reviewed by a qualified professional.