Source: https://seerepo.com/compare/calcom/cal.diy/vs/vercel/next-forge
Markdown source: https://seerepo.com/compare/calcom/cal.diy/vs/vercel/next-forge.md
Description: cal.diy and next-forge share 20 technologies: Next.js, Postgres, Redis, Sentry, Stripe, React, @next/third-parties, Vercel, PostHog, Zod, Tailwind CSS, next-themes, class-variance-authority, React Hook Form, sonner, Radix UI, Lucide, tailwind-merge, cmdk, and react-day-picker. Both are written in TypeScript.

# cal.diy vs next-forge

cal.diy and next-forge share 20 technologies: Next.js, Postgres, Redis, Sentry, Stripe, React, @next/third-parties, Vercel, PostHog, Zod, Tailwind CSS, next-themes, class-variance-authority, React Hook Form, sonner, Radix UI, Lucide, tailwind-merge, cmdk, and react-day-picker. Both are written in TypeScript.

- [calcom/cal.diy](https://seerepo.com/r/calcom/cal.diy): Scheduling infrastructure for absolutely everyone.
- [vercel/next-forge](https://seerepo.com/r/vercel/next-forge): Production-grade Turborepo template for Next.js apps.

## What they share and what sets them apart

- In common: Next.js, Postgres, Redis, Sentry, Stripe, React, @next/third-parties, Vercel, PostHog, Zod, Tailwind CSS, next-themes, class-variance-authority, React Hook Form, sonner, Radix UI, Lucide, tailwind-merge, cmdk, react-day-picker
- Only in cal.diy: connect, NestJS, @nestjs/bull, @nest-lab/throttler-storage-redis, bull, Google, @trpc/server, tRPC, lru-cache, kysely, next-auth, helmet, class-validator, class-transformer, @axiomhq/winston, nest-winston, tslog, winston, winston-transport, classnames, TanStack, Framer, @formkit/auto-animate, react-select, @hookform/error-message, react-digit-input, react-inlinesvg, @dub/embed-react, Glide, kbar, react-phone-input-2, react-sticky-box, react-timezone-select, react-turnstile, jose, otplib, markdown-it, qrcode, react-qr-code, @hookform/resolvers, @todesktop/client-core, ink, ink-text-input, ink-select-input, @googleapis/oauth2, ical.js, Base UI, entities, nodemailer, bcryptjs, handlebars, @trigger.dev/sdk, @sendgrid/client, dompurify, jimp, remove-markdown, sanitize-html, sharp, turndown, marked, Prisma, node-html-parser, node-ical, lexical, react-easy-crop, react-colorful, @lexical/markdown
- Only in next-forge: Svix, OpenAI, Clerk, Resend, ai, streamdown, @clerk/themes, geist, embla-carousel-react, input-otp, react-resizable-panels, recharts, vaul, @radix-ui/react-icons, @react-email/components, @logtail/next

## Side by side

| | cal.diy | next-forge |
|---|---|---|
| Size | 554,770 lines written, 4,286 code files | 26,893 lines written, 199 code files |
| Who writes it | 6.3% of its commits signed by AI. With Devin, Claude Code, CodeRabbit, Cursor, and GitHub Copilot | 0.6% of its commits signed by AI. With Claude Code and GitHub Copilot |
| Activity | Last push November 13, 2026, 16,072 commits, 50,151 stars | Last push May 28, 2026, 1,489 commits, 7,790 stars |
| Tests | 645 test files. 14.9% of its code files have a test that imports them | 3 test files. 1.5% of its code files have a test that imports them |

- Size: Lines written by people and agents, without generated ones; code files, without tests.
- Who writes it: A commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
- Activity: From GitHub and its history, on the day SeeRepo read it.
- Tests: The files that test the code, and the share of code files a test imports.

## Frequently asked questions

### Which is bigger, cal.diy or next-forge?

cal.diy, with 554,770 lines written; next-forge has 26,893.

The proof: [calcom/cal.diy's code at commit ae027bb](https://github.com/calcom/cal.diy/tree/ae027bb70e694e2d2c44569f398d6cbcee0389b1)

### Which has more GitHub stars, cal.diy or next-forge?

cal.diy, with 50,151 stars; next-forge has 7,790.

The proof: [calcom/cal.diy on GitHub](https://github.com/calcom/cal.diy)

### Which has more tests, cal.diy or next-forge?

cal.diy, with 645 test files; next-forge has 3.

The proof: [calcom/cal.diy's code at commit ae027bb](https://github.com/calcom/cal.diy/tree/ae027bb70e694e2d2c44569f398d6cbcee0389b1)

### Which was updated more recently, cal.diy or next-forge?

cal.diy: its last push was on November 13, 2026, and next-forge's on May 28, 2026.

The proof: [calcom/cal.diy's commits on GitHub](https://github.com/calcom/cal.diy/commits)

### Which has more commits signed by AI, cal.diy or next-forge?

cal.diy: an AI signed 6.3% of its commits, with Devin, Claude Code, CodeRabbit, Cursor, and GitHub Copilot; in next-forge, 0.6%.

The proof: [the commits each tool signed in calcom/cal.diy](https://seerepo.com/r/calcom/cal.diy/ai)

## Sources

- calcom/cal.diy: Read on November 18, 2026, at commit ae027bb (https://github.com/calcom/cal.diy/tree/ae027bb70e694e2d2c44569f398d6cbcee0389b1)
- vercel/next-forge: Read on November 18, 2026, at commit f189de7 (https://github.com/vercel/next-forge/tree/f189de79ceef7c1ef69f61f12e272f99b4cdb699)

## What is your repo built with?

Any public repo, with no account: https://seerepo.com/r/owner/repo/built, with the owner and name it has on GitHub.
