---
title: "Deploy Calendar Workbench"
description: "Printable calendars, ISO weeks, Julian dates, and a tiny calendar API."
category: "Starters"
url: https://railway.com/deploy/calendar-workbench
---

# Deploy Calendar Workbench

Printable calendars, ISO weeks, Julian dates, and a tiny calendar API.

**[Deploy Calendar Workbench on Railway](https://railway.com/template/calendar-workbench)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/calendar-workbench/manifest.json

- **Creator:** Mateo Pedersen's Projects
- **Category:** Starters

## Template content

### calendar-workbench

- **Source:** mateopedersen/calendar-workbench
- **Health check:** /health
- **Public domain:** Yes

## Documentation

# Deploy and Host Calendar Workbench on Railway

Calendar Workbench is an open-source tool for print-ready Gregorian calendars, ISO week checks, Julian/Gregorian conversion, and a small JSON API with OpenAPI documentation.

## About Hosting Calendar Workbench

Deploy the public GitHub repository as one Railway service. Railway builds the included Dockerfile and starts the Node.js server on the platform-provided PORT. The app needs no database, account setup, or environment secrets. The template configures the HTTP proxy for port 8080 and checks /health before a deployment completes.

## Common Use Cases

- Create printable monthly and yearly calendars in A4 or US Letter layouts.
- Inspect leap years, ISO week-year boundaries, and UTC-safe date behavior.
- Convert proleptic Julian and Gregorian dates or integrate calendar data through JSON endpoints.

## Dependencies for Calendar Workbench Hosting

- Node.js 20 or newer (included in the Docker build).
- No database, external runtime packages, or required environment variables.

### Implementation Details

The service listens on Railway's PORT (8080 by default locally), exposes a /health endpoint, and serves the web app, API, and OpenAPI schema from one process. For an always-on demo, keep one replica. Railway Serverless can reduce idle compute usage, with a possible cold start on the next request.

## Why Deploy Calendar Workbench on Railway?

Railway builds and runs the service from GitHub, provides a public HTTP endpoint, and handles health checks and deployment updates. Start with the resources included in your plan and monitor Usage while a demo is live.

## Source Code & Documentation

- Source: https://github.com/mateopedersen/calendar-workbench
- Live demo: https://calendar-workbench-production.up.railway.app/
- API guide: https://calendar-workbench-production.up.railway.app/docs
- OpenAPI: https://calendar-workbench-production.up.railway.app/openapi.json
- Calendar references: https://www.betacalendars.com/ · https://www.betacalendars.com/january-calendar.html · https://www.betacalendars.com/monthly-calendar

Calendar Workbench is an independent project and is not affiliated with BetaCalendars.

## Similar templates

- [open-excalidraw](https://railway.com/deploy/open-excalidraw) — Self-hostable collaborative drawing built on Excalidraw
- [caring-vibrancy](https://railway.com/deploy/caring-vibrancy) — Deploy and Host caring-vibrancy with Railway
- [Appsmith](https://railway.com/deploy/appsmith-1) — Low-code platform for internal tools, dashboards, and admin panels.

Open this page in a browser: https://railway.com/deploy/calendar-workbench