Deploy and Host CalendarForge Cloud on Railway

CalendarForge Cloud is an independent open-source calendar planning studio and API by Ethan, maker of Make a Calendar. Version 0.1.0 provides Gregorian calendars, US observed holidays, business-day math, 4-4-5 retail periods, JSON/CSV/ICS exports, and PostgreSQL project APIs. Source: GitHub.

Live resources: Open the CalendarForge demo · API and developer documentation · OpenAPI schema · Health check · Public calendar resource directory.

About Hosting CalendarForge Cloud

This template creates a Next.js web service and a private PostgreSQL database in your Railway workspace. Railway builds the web app from the public repository. The app's DATABASE_URL references the database's private connection. Enter a strong, unique CALENDARFORGE_API_TOKEN when Railway prompts you; keep it private and send it only over TLS. This token protects PostgreSQL project endpoints. Calendar events in the public demo are saved in the current browser and do not share the template deployment's database. Review your Railway plan and current usage before leaving services running.

Common Use Cases

View month grids, ISO week numbers, and observed US federal holidays.
Count business days or add/subtract workdays.
Review 4-4-5 retail periods.
Export JSON, CSV, and ICS data.
Save trusted operator projects through the token-protected API.
Visit complementary printable calendars, business-day tools, pay-period calendars, retail calendars, iCalendar, and date tools.

Dependencies for CalendarForge Cloud Hosting

Railway web service built from the public GitHub repository.
Railway PostgreSQL service connected over private networking.
A strong, unique CALENDARFORGE_API_TOKEN for persisted project endpoints.

Railway provides the runtime and database. No external API is required.

Why Deploy CalendarForge Cloud on Railway?

Run the source and PostgreSQL data in a Railway project you control. The template connects the web service and database and builds the app from source. Railway compute and database usage may consume credits based on your workspace plan and runtime.

Release scope and conventions

This is a deployable v0.1.0 foundation, not a multi-user SaaS. The project API uses one shared bearer token and has no user accounts or workspace isolation. There is no background worker or PDF export. Confirm the documented Sunday-nearest-February-1 4-4-5 convention against your own fiscal policy. CalendarForge is separate from Make a Calendar and does not call its private services.