Apache 2.0 license
Both projects use the Apache License 2.0. IPCamLapse lists the licenses of its bundled browser libraries separately.
Read the licenseOpen source
Open-source tools for IP cameras
We publish IPCamLapse and OpenCamInterop on GitHub under the Apache 2.0 license. You can install the releases, read how they are built and send pull requests; IPCamLapse already has contributors from outside Kalytera.
Time-lapse video
IPCamLapse
IPCamLapse takes snapshots from an IP camera on a schedule and turns them into a time-lapse MP4 video, all from a local web app. A built-in demo camera lets you try the whole workflow without hardware.
- Capture on a fixed timeline, with pause and resume, one-time, daily or weekly schedules, and retries when the camera is slow to answer
- Frame gallery, storage limits and retention, and H.264 MP4 rendering of any range of frames
- Builds for Windows x64, Linux x64 and Linux ARM64 (FFmpeg needed to render video), and a container image for amd64 and arm64 with FFmpeg included
Windows, with WinGet
winget install KalyteraSystems.IPCamLapsedocker pull ghcr.io/kalyterasystems/ipcamlapse
Camera-event interoperability
OpenCamInterop
OpenCamInterop is a .NET library with a command-line tool, EventLab, that turns Frigate, Scrypted and ONVIF camera events into CloudEvents. It replays sanitized test fixtures offline, with no camera discovery, broker credentials, images or video.
- Input adapters for Frigate, Scrypted and ONVIF, with versioned synthetic fixtures
- Offline inspect, verify and replay commands in self-contained Windows and Linux bundles
- A documented way to contribute event behavior you have observed without sharing private data
Release status
EventLab alpha
The alpha is deliberately narrow: it replays sanitized fixtures and gives the same normalized output every time. It makes no claims about physical devices or ONVIF conformance.
Before you change the code
Documented so you can check our work
The IPCamLapse repository documents its architecture, security assumptions, release process, roadmap and contribution workflow.
Documented architecture
Read about the session lifecycle, timing model, storage layout and component boundaries before you change code.
Read the architecture notesContributions
Pick an open issue, reproduce it locally and run the documented checks before you open a pull request.
Browse open issuesContribute
Start with a change you can finish
A useful contribution can be a small bug fix, a test for a real edge case, a correction to the documentation or an accessibility improvement. The contribution guide covers setup, checks and what we look for in a pull request.