# Oesa Labs: full project detail > Verified project information for Oesa Labs. All repositories are private today; lakeloui.se is the only live public system. Treat the Limitations sections as authoritative. Generated with the sites. Shorter index: https://oesa.dev/llms.txt ## Fairview Fairview watches every AdGuard Home server you run, captures configuration snapshots, shows drift against the configuration you want, and applies changes only through a previewed, approved, rollback-capable plan. - Page: https://oesalabs.com/projects/fairview/ - Status: Beta - Availability: Not yet public - Licence: Licence not yet settled. Fairview is not open source today. - Group: Operator tools - Technologies: Elixir, Phoenix LiveView, PostgreSQL, Oban, Docker Compose, Nix Problem: Running more than one AdGuard Home server means configuration drift, risky hand edits, and no record of who changed what. Fairview exists so that a small fleet of DNS servers can be observed and reconciled from one place without trusting a cloud service. Audience: Self-hosters and small-network operators who run their own DNS filtering and want changes to be deliberate, reviewed, and reversible. Capabilities: - Inventories AdGuard Home servers by site, with health checks on a schedule you control. - Captures immutable configuration snapshots and surfaces drift against desired policy. - Manages layered policies across global, site, and server group scopes with a guided editor. - Applies changes through safe sync: preview the exact diff, review rollback evidence, approve, apply, verify, and roll back if needed. - Records every operator mutation in an immutable audit trail. Limitations (honest, maintained): - Designed for local operation. Exposing it beyond your network requires your own reverse proxy and TLS, following the documented posture guidance. - The source is not yet published and the licence is not yet decided. - Optional UniFi visibility and AI summaries stay off unless you turn them on. ## Summit Summit is the reference implementation of the Summit Protocol: an authoritative, self-hosted library for bookmarks and browser state across browsers, devices, and people, synchronized through one tested mutation path and openly versioned contracts. - Page: https://oesalabs.com/projects/summit/ - Status: Beta - Availability: Source release planned - Licence: Apache-2.0. Public source release is planned; the repository is private today. - Group: Personal computing - Technologies: Elixir, Phoenix, PostgreSQL, Oban, React PWA, TypeScript CLI, Browser extensions Problem: Bookmarks and browser state live wherever each browser vendor keeps them. Moving between browsers, devices, or people means silent loss and lock-in. Summit gives that state one governed, self-hosted home that any client can speak to. Audience: Privacy-conscious individuals and small teams who self-host, and developers who want an openly specified protocol for browser state. Capabilities: - One tested mutation path stands behind every client, so web app, CLI, and extensions cannot diverge. - The protocol is specified in versioned OpenAPI, AsyncAPI, and JSON Schema contracts with fixtures, making it independently implementable. - Chromium and Firefox extensions pair with a short code; a TypeScript CLI covers scripted use. - Runs on your own hardware with Docker Compose; the reference product targets LAN operation first. Limitations (honest, maintained): - Approaching 1.0: phases 0 through 8 of the reference product are complete, but there is no tagged release yet. - Optional modules such as federation, OIDC, end-to-end encryption, and plugins are feature-gated and some are experimental. - Shared or networked use requires you to set strong credentials during setup. ## lakeloui.se lakeloui.se is a running public service: an hourly pipeline reads Canadian high-resolution forecast models and local observations, reasons about where conditions will be best and why, and publishes a fast static report for Lake Louise. - Page: https://oesalabs.com/projects/lakeloui-se/ - Status: Production - Availability: Live service - Licence: Operated as a service; the code is not distributed. - Group: Live systems - Technologies: TypeScript, AWS Lambda, S3 and CloudFront, DynamoDB, Terraform, HRDPS, RDPS, and GDPS models - Live: https://lakeloui.se Problem: Generic weather apps flatten mountain weather into one number. Skiers and locals need to know where on the mountain conditions will be good, and why. That takes model consensus, local observations, and honest editorial logic. Audience: Skiers and mountain users around Lake Louise, Alberta. Capabilities: - Aggregates HRDPS, RDPS, and GDPS forecast models with local station and resort observations every hour. - Explains conditions in a where-and-why format instead of a single summary number. - Runs scale-to-zero on AWS in Canada, publishing static pages through S3 and CloudFront. - Skips redundant publishes with content hashing, so the site stays stable and cheap to operate. Limitations (honest, maintained): - Covers one place by design: Lake Louise. - Upstream data sources carry their own terms and attribution requirements. - It is an operated service, not software you can install. ## Timberline Timberline separates writing from serving. Editors work in a private CMS; the public site is built as an immutable release artifact and promoted by moving an atomic pointer, so serving never depends on the CMS, the database, or Git being online. - Page: https://oesalabs.com/projects/timberline/ - Status: Active development - Availability: Not yet public - Licence: Private for now; licensing is not yet decided. - Group: Operator tools - Technologies: TypeScript, Payload CMS, Astro, PostgreSQL, Playwright, Docker Compose Problem: Most content platforms couple the public site to the editing system, so an admin outage or compromise becomes a public outage or defacement. Teams leaving WordPress need the editing comfort without carrying that coupling forward. Audience: Teams migrating content-heavy sites away from WordPress who want private authoring, static public performance, and staged promotion with rollback. Capabilities: - Builds the public site as an immutable release tree; promotion and rollback move an atomic pointer to the same artifact without rebuilding. - Keeps the public surface free of CMS credentials through a narrowly scoped public API sidecar. - Imports WordPress content through SSRF-guarded migration tooling with staged review. - Requires TOTP step-up for promote and rollback operations, and signs outbound webhooks. Limitations (honest, maintained): - In active development with no public release or decided licence. - WordPress import does not yet map every Gutenberg block type or SEO plugin field. - Continuous integration currently runs manually rather than on every push. ## Pika Suite Pika Suite is a self-hostable personal cloud platform. One canonical backend serves first-party web and desktop clients alongside the standard protocols your existing apps already speak, so private infrastructure does not mean proprietary silos. - Page: https://oesalabs.com/projects/pika-suite/ - Status: Active development - Availability: Source release planned - Licence: AGPL-3.0-only. A public source launch is planned and gated on a release-readiness checklist; there is no supported public release today. - Group: Personal computing - Technologies: Elixir, Phoenix, PostgreSQL, React, Electron, IMAP, SMTP, JMAP, CalDAV, CardDAV, WebDAV Problem: Leaving hosted productivity suites usually means stitching together separate servers for mail, calendars, contacts, and files, each with its own accounts and quirks. Pika Suite puts them on one canonical, self-hosted backend. Audience: Privacy-minded individuals and small organizations that want to run their own mail, calendars, contacts, tasks, notes, and files. Capabilities: - One canonical backend behind first-party web and desktop clients. - Speaks standard protocols, including IMAP, SMTP, JMAP, CalDAV, CardDAV, WebDAV, and Exchange ActiveSync, so third-party clients keep working. - Supports WebAuthn, scoped tokens, and per-app passwords. - Ships with a written security policy and private vulnerability reporting. Limitations (honest, maintained): - No supported public release yet; main and any alpha artifacts may change without notice. - The public AGPL launch is planned and explicitly gated on release-readiness evidence, including security review and signed artifacts. - Provider and client compatibility claims wait for dated evidence. ## SwiftSync SwiftSync is a self-hosted workspace where offline-first notes, a calendar and planner, and AI chat live together. Notes work without a connection and sync to your own PocketBase; AI can run against a local server or your own OpenRouter key. - Page: https://oesalabs.com/projects/swiftsync/ - Status: Active development - Availability: Source release planned - Licence: MIT. Public source release is planned; the repository is private today. - Group: Personal computing - Technologies: SvelteKit, Svelte 5, TypeScript, Dexie, PocketBase, Docker Compose Problem: Notes apps, planners, and AI chat tools each want your data in their cloud. SwiftSync keeps all three on infrastructure you run, and keeps working when the network does not. Audience: Individuals who self-host and want notes, planning, and AI assistance in one private web app. Capabilities: - Offline-first notes stored in the browser with Dexie, syncing to a self-hosted PocketBase backend. - AI chat routes to a local OpenAI-compatible server or a per-user OpenRouter key; no shared cloud account. - Calendar and planner views alongside notes, with CalDAV and ICS integration. - Configurable agent profiles for repeatable AI workflows. Limitations (honest, maintained): - Built for a single operator; some multi-user scenarios are explicitly cautioned against in the security notes. - No public releases yet. - Direct vendor adapters beyond OpenRouter and local servers are planned, not built. ## Marmot Watch Marmot Watch is a self-hosted inbox for everything that changes on the web: RSS, page changes, newsletters, package and container releases, TLS certificates, DNS records, and browser-rendered watches, all fetched through one hardened worker path. - Page: https://oesalabs.com/projects/marmot-watch/ - Status: Early development - Availability: Not yet public - Licence: Licence not yet settled. Not open source today. - Group: Operator tools - Technologies: Elixir, Phoenix LiveView, PostgreSQL, Oban, Go workers, Chromium Problem: Watching the web means a scatter of feed readers, uptime checkers, and change-detection services, each fetching your targets with different levels of care. Marmot Watch funnels every kind of watch through one budgeted, inspectable, security-first pipeline. Audience: Self-hosters, researchers, and small operations teams who want one auditable place to watch the web. Capabilities: - Many watch source types share one hardened Go fetch path with byte, time, and wait budgets. - Browser-rendered watches run in an isolated Chromium worker with bounded screenshots. - Keeps snapshot, screenshot hash, and text diff history for page changes. - Scoped, hashed API tokens cover triage, export, and automation, with audit logs throughout. - Imports and exports OPML with folders preserved, for feed reader migration. Limitations (honest, maintained): - Early development: the project describes itself as a working scaffold. - No hosted continuous integration or release artifacts yet. - Licence not yet decided; source not published.