snagtime README

The project's README from github.com/nateherkai/snagtime. As one markdown file: README.md.

SnagTime

Snag a time. Get booked.

A free, self-hostable scheduling app for availability, booking links, calendar sync, email notifications, and test payments.

What SnagTime does

SnagTime gives you the source code for your own scheduling system. You can run it locally for free, customize it, and host it on infrastructure you control.

Set it up with Codex or Claude Code

You can give an AI coding assistant this repository URL and have it handle the local installation while it pauses for the account steps only you can complete.

Open AI-assisted setup, copy the student prompt, and paste it into Codex or Claude Code with this repository link:

https://github.com/nateherkai/snagtime

The guide separates the credential-free local demo, optional integrations, and advanced public deployment so the assistant does not pull you into infrastructure work before the app runs locally.

Five-minute local setup

Requirements

1. Clone and enter the repository

git clone https://github.com/nateherkai/snagtime.git
cd snagtime

2. Generate your local configuration

npm run setup

The setup command creates an ignored .env.local, generates independent cryptographic secrets, and prints the local demo login once. You can provide your own organizer login instead:

npm run setup -- --email [email protected] --password "YourStrong!Password7"

3. Install, prepare the database, and start SnagTime

npm run demo:free

Open http://localhost:3000 and use the login printed by the setup command.

The credential-free local mode uses SQLite, a local calendar adapter, a local email inbox, and stub payments. It does not call Google or Stripe.

Connect your services

Copying the repository gives you all of the software. External integrations still belong to you and must be configured with your own accounts.

Capability What you provide Required for local demo?
Database Nothing for SQLite, PostgreSQL for production No
Public hosting HTTPS domain plus a long-running Node web service and worker No
Google Calendar OAuth client ID and client secret No
Transactional email SMTP host, user, password, and verified sender domain No
Stripe payments Stripe test secret, publishable key, and webhook secret No

See Integration setup for exact callback URLs, environment variables, and verification steps.

Put it on the internet

SnagTime is a dynamic application, not a static website. It needs server-side Node.js execution, a persistent database, webhook endpoints, and a continuously running background worker.

The full production architecture is intentionally strict. It uses PostgreSQL 18, forced row-level security, separate app and worker credentials, verified database TLS, and authenticated proxy ingress. Read Deployment guide before choosing a host.

What is actually free?

The SnagTime source code is free under the MIT License. Running it locally can also cost nothing.

A public deployment can still create third-party costs:

Google OAuth credentials can be created without paying SnagTime. Stripe test mode is free for testing. This release deliberately rejects Stripe live-mode keys, so do not advertise it as a live payment processor without implementing and auditing live-mode support.

Useful commands

npm run setup          # Create .env.local and local credentials
npm run setup:check    # Validate the credential-free local configuration
npm run demo:free      # Install, migrate, seed, and run the free local demo
npm run dev            # Run the configured local development server
npm run test           # Run the unit and contract test suite
npm run typecheck      # Check TypeScript
npm run lint           # Run ESLint
npm run build          # Create the Next.js production build
npm run ci:secret-scan # Scan public source files for credential patterns

Database commands:

npm run db:generate
npm run db:migrate
npm run db:seed

npm run db:reset destroys the local SQLite database. Use it only when you intentionally want a clean demo.

Project structure

apps/web/             Next.js application and API routes
apps/web/public/      SnagTime logo and icon
prisma/               SQLite schema, PostgreSQL schema, and migrations
scripts/              Setup, database, worker, security, and verification tools
infrastructure/       PostgreSQL container hardening
tests/                Browser and end-to-end tests
docs/                 Setup, deployment, and brand documentation

Project status

The local SQLite experience and integration test paths are designed for demos, development, and personal experimentation. The production architecture is an advanced self-hosting path, not a one-click managed service. You are responsible for infrastructure security, backups, provider configuration, deliverability, compliance, and ongoing operations.

Please read Security before exposing a deployment publicly.

Contributing

Issues and pull requests are welcome. See CONTRIBUTING.md.

License

SnagTime is available under the MIT License.

snagtime (nateherkai/snagtime)

scheduling
Searching Database…

389 ·GitHub
Snagtime
What is this?SnagTime is a free, self-hostable scheduling app: it gives you the source code for booking links, availability management, Google Calendar sync, SMTP email notifications, and Stripe test-mode payments.
Is this a hosted service like Calendly, or something I run myself?It is self-hosted: you get the full source code to run locally, customize, and deploy on infrastructure you control, not a SaaS you sign up for.
How do I get it running?Clone the repo, run `npm run setup` to generate a local .env.local with cryptographic secrets, then install dependencies and start it - the whole credential-free local demo takes about five minutes using SQLite.
What do I need installed before trying it?Just Node.js 20.9+ (Node 24 is the verified runtime), npm, and Git - no Google or Stripe accounts are required for the local demo.
Can I deploy this to Vercel?No - Vercel isn't supported out of the box because production requires a long-running background worker plus PostgreSQL runtime roles; you need a Linux VPS or a container platform instead.
Does it process real payments through Stripe?No - this release deliberately rejects Stripe live-mode keys, so only Stripe test-mode payments work; you'd have to implement and audit live-mode support yourself.
Can I set this up with an AI coding assistant instead of doing it manually?Yes - you can give Codex or Claude Code the repository URL and a provided student prompt, and it will handle local installation while pausing for account steps only you can complete.
What database does production use versus the local demo?The local demo runs on SQLite with no external accounts needed, while production uses PostgreSQL 18 with forced row-level security, separate app/worker credentials, verified TLS, and authenticated proxy ingress.
What can I customize on the booking pages?Workspace branding, accent colors, profile images, and uploaded logos, plus event types with multiple durations, custom booking questions, and time-zone-aware availability.
What are similar projects?open-saas, crm, documenso, golive-skill, cohort-harbor, cal.diy, inbox-zero, gptibo
Which topics is it in?scheduling, prisma, stripe, open-source-alternative, payments, email, oauth, authentication, nextjs, sqlite, postgresql, web-app
Creator
nateherkai
Size
0.5 MB
Stars
389
Updated
CommitAug 28
Age
1mo
Commits · 90 Days