Docs Contact support
Docs menu

Requirements

What you need before you install: a Linux or Mac server, or Docker, a domain with HTTPS, and optionally email and Stripe.

Updated Nov 14, 2026 3 min read

This page lists what you need to run ChronoSlice, and what you need only if you want email, online payments or the Mac app.

The server

Pick one of these three:

  • Linux on x86_64 or arm64. Run uname -m to check. x86_64 is the x86_64 build, and aarch64 is the arm64 build. See Install on Linux.
  • A Mac with macOS 11 (Big Sur) or later. The macOS build is universal, so one download runs on Apple silicon and Intel. It's signed and notarized. See Install on macOS.
  • Docker. The image ghcr.io/skulkworks/chronoslice comes for linux/amd64 and linux/arm64. See Run with Docker.

The rest applies to all three:

  • Nothing else installed. The builds are static, with no dependencies. You don't need Rust, Node or a database server. A container runtime is needed only for the Docker image.
  • systemd is what the Linux guide uses to keep ChronoSlice running, and what chronoslice update restarts. On a Mac, the guide uses launchd, and chronoslice update restarts that. Other ways of running a program work too, but then you restart it yourself after an update. In Docker, you update by pulling the new image.
  • Memory. A server with 1 GB of memory is plenty for a small team.
  • Disk. The program is about 60 MB on Linux, and about 145 MB on a Mac, where one file holds the Apple silicon and Intel builds. The database is one file, and it grows with your time entries, invoices and attached files. A new database is under 1 MB, and ten years of a small agency's history came to 18 MB. Leave room for backups. Every chronoslice update keeps a full copy of the database.

A domain name and HTTPS

  • A domain name that points to the server, such as time.example.com.
  • HTTPS. ChronoSlice itself listens on plain HTTP at 127.0.0.1:7340, and a reverse proxy in front of it handles HTTPS. Reverse proxy and HTTPS shows Caddy, which gets certificates for you, and nginx.

You need HTTPS for more than looks:

  • The Mac app only signs in to addresses that use HTTPS, apart from addresses on your own machine.
  • The sign-in cookie should be marked Secure.
  • Stripe only sends payment notices to an https:// address.
  • Links in emails to clients should point to a secure address.

Network access from the server

  • During the trial the server doesn't contact anyone. It sends nothing to chronoslice.app until you enter a licence key.
  • With a licence key, it needs to reach https://chronoslice.app over HTTPS. It does that when you enter or check the key, once a day, and when you run chronoslice update. See Buying and entering a licence.
  • Email needs a route to your SMTP server.
  • Stripe needs a route to Stripe's API.

Optional

  • An SMTP account to send invoices, reminders and receipts. Postmark, Amazon SES, Resend, Fastmail or your own mail host all work. Set up SPF and DKIM for the sending domain so invoices don't land in spam. See Email.
  • A Stripe account if clients will pay online. See Getting paid with Stripe.
  • A Mac with macOS 26 or later for the Mac app. See Installing and signing in.
  • A place for backups, such as a second disk or an S3-compatible bucket. See Backups and restoring.

Ready?

Quick start takes about ten minutes. Install on Linux, Install on macOS and Run with Docker explain every step.

Was this helpful?

Still stuck?

Send us a request: it goes to the people who build ChronoSlice, and the reply comes by email. Include your ChronoSlice version (Settings › Licence shows it) and what you tried.