NexCal

Spec sheet

What it does

NexCal is a self-hosted appointment-booking platform for organizations with multiple practitioners.Read 15 Oct 2026 · github.com

Purpose

NexCal is a self-hosted appointment scheduling platform for multi-provider teams such as clinics, salons, consulting firms and studios.Read 1 Oct 2026 · github.com

Deployment

Production deployment requires Docker and Docker Compose, and the recommended launch command starts the application with PostgreSQL.Read 1 Oct 2026 · github.com

Integrations

NexCal integrates with WhatsApp through MultiWA, Google Calendar, Google Meet and Midtrans payments; its payment architecture is extensible to Xendit and Stripe.Read 1 Oct 2026 · github.com

Security

Authentication uses cookies with bcrypt hashing, and booking creation applies Zod validation plus a real-time availability re-check.Read 1 Oct 2026 · github.com

Support

The project welcomes contributions, issues and feature requests.Read 1 Oct 2026 · github.com

License

The repository is released under the MIT License, including permission to use, modify, distribute and sell the software subject to the license notice.Read 15 Oct 2026 · raw.githubusercontent.com

Maker

The repository owner is Rizky Bachtiar Irwanto, a full-stack developer based in Batam, Indonesia.Read 15 Oct 2026 · github.com

Analytics

The administrator dashboard reports revenue, 30-day trends, top services, staff performance and operational metrics.Read 15 Oct 2026 · github.com

Booking

Customers choose a practitioner, service and time slot through a provider-aware booking flow.Read 1 Oct 2026 · github.com

Booking flow

Customers select a practitioner, service and time through a provider-aware booking wizard.Read 15 Oct 2026 · github.com

Calendar integration

Confirmed bookings can be pushed one way into a provider's Google Calendar.Read 15 Oct 2026 · github.com

Data hosting

The project states that data does not leave the user's server and that organizations have isolated data by default.Read 1 Oct 2026 · github.com

Data hosting claim

The project says its self-hosted deployment keeps data on the operator's server and avoids vendor lock-in.Read 15 Oct 2026 · github.com

Developer interface

The documented extension point is a PaymentProvider interface and factory for adding payment gateways.Read 15 Oct 2026 · github.com

Documentation depth

Usage documentation covers Docker deployment, local npm development, database setup, environment variables and repository structure.Read 15 Oct 2026 · github.com

Double-booking protection

Booking creation validates time ranges with Zod and rechecks live availability for pending and confirmed bookings.Read 15 Oct 2026 · github.com

Down payments

Services can require a percentage deposit, full payment or no payment.Read 15 Oct 2026 · github.com

Environment requirements

Required server settings include a PostgreSQL connection, Auth.js secret, trusted-host setting and public application URL.Read 15 Oct 2026 · raw.githubusercontent.com

Independent listing

IndieStack categorizes NexCal as an open-source scheduling and booking tool and reports it was updated 75 days before its page crawl.Read 15 Oct 2026 · indiestack.ai

Independent listing: activity

IndieStack shows 28 developer visits during the displayed month and labels the project actively maintained.Read 15 Oct 2026 · indiestack.ai

Independent listing: adoption

IndieStack reports zero AI-agent recommendations and two total citations for the listing.Read 15 Oct 2026 · indiestack.ai

Independent listing: related tools

IndieStack lists notifuse, Strapi, Ory, react-jsonschema-form, Thanos, react-three-fiber, Sim and Payload under confirmed compatibility.Read 15 Oct 2026 · indiestack.ai

Independent listing: repository metadata

IndieStack identifies the project as TypeScript and reports its last commit as 76 days before the page crawl.Read 15 Oct 2026 · indiestack.ai

Installation

The documented production setup requires Docker and Docker Compose, then starts with docker compose using the production file.Read 15 Oct 2026 · github.com

Limit: deployment operations

The deployment table says Docker-on-VPS installations require manual SSL and updates.Read 15 Oct 2026 · github.com

Limit: documentation inconsistency

The README describes virtual consultations as completed in v2.5, while ROADMAP.md describes virtual consulting as proposed v3 functionality.Read 15 Oct 2026 · github.com

Limit: planned work

The roadmap lists recurring bookings, multilingual support, PWA push notifications and shared multi-tenant SaaS mode as future v3 work.Read 15 Oct 2026 · github.com

Maker focus

The maker's profile lists enterprise SaaS, WhatsApp APIs, real-time systems and self-hosted solutions as focus areas.Read 15 Oct 2026 · github.com

Operations

Administrators can filter bookings, change statuses, record cash payments, edit schedules, add date overrides and configure services.Read 15 Oct 2026 · github.com

Package version

package.json identifies the application as version 2.1.0 and marks it private.Read 15 Oct 2026 · raw.githubusercontent.com

Patient portal

Customers receive a management link for booking status, invoices, meeting links, rescheduling and cancellation up to 24 hours before the appointment.Read 15 Oct 2026 · github.com

Payment extensibility

Payment providers use a gateway-agnostic plugin pattern, with Midtrans included and Stripe or Xendit described as extendable options.Read 15 Oct 2026 · github.com

Payments

The booking flow supports Midtrans Snap payments configured from the administrator interface.Read 15 Oct 2026 · github.com

Planned features

Recurring bookings, multilingual support, a progressive web app and shared multi-tenant SaaS mode are listed as future features.Read 1 Oct 2026 · github.com

Provider management

Organizations use OWNER and STAFF roles, with provider-specific schedules and access controls.Read 15 Oct 2026 · github.com

Repository activity

GitHub displays 9 stars, 11 forks, one open issue and 21 commits for the repository.Read 15 Oct 2026 · github.com

Roadmap status

ROADMAP.md calls v2.4.0 stable and feature-frozen while accepting bug fixes and community contributions.Read 15 Oct 2026 · github.com

Scheduling

The scheduling engine supports per-service buffer times, real-time filtering of past slots and recycling of cancelled slots.Read 1 Oct 2026 · github.com

Scheduling engine

Per-service buffer times, past-time filtering and cancelled-slot recycling are part of the scheduling engine.Read 15 Oct 2026 · github.com

Security stated

Authentication uses cookie-based sessions with bcrypt password hashing.Read 15 Oct 2026 · github.com

Target users

The project names clinics, salons, consulting firms, studios and other multi-provider businesses as target users.Read 15 Oct 2026 · github.com

Team access

Organizations use OWNER and STAFF roles with role-based access control and provider-specific management.Read 1 Oct 2026 · github.com

Technology

The stack uses Next.js 16, TypeScript 5, PostgreSQL 16, Prisma 7, Auth.js v5, Tailwind CSS 4 and Docker.Read 15 Oct 2026 · github.com

Virtual consultations

Services can generate Google Meet links automatically after an administrator confirms a booking.Read 1 Oct 2026 · github.com

Virtual meetings

The README describes automatic Google Meet link generation for virtual services.Read 15 Oct 2026 · github.com

WhatsApp integration

WhatsApp booking and payment notifications use the MultiWA API with URL, key and session settings.Read 15 Oct 2026 · github.com

Plans and prices

Every NexCal plan and price →

Where Specifiction places it

• Salon Appointment Scheduling Software#14 of 338.4