What Periskopos is
Each app you run in production lives across a host, a database, a domain, CI, maybe a payments account and an error tracker, each with its own dashboard. Periskopos is a desktop app that reads them all and tells you, in one window, what’s down, whether your last push actually went live, what’s misconfigured and what’s about to expire, before a user does.
You connect each account (Cloudflare, GitHub, Render, Supabase, Vercel, Stripe…) once with a key you create, and Periskopos suggests what to watch for each app. Nothing changes in your apps.
How it works
Section titled “How it works”- It runs on your computer. The server listens on
127.0.0.1only and opens only in its own window. There’s no Periskopos account and no cloud. - Your keys stay there. They live in one file in your profile, outside any project, and go nowhere except to the provider they belong to. No page or tool ever returns one.
- It only reads, unless you switch on actions for an account. Every action is confirmed, and dangerous ones ask you to type the app’s name.
- AI assistants can ask, never act. Claude, Cursor, VS Code and others connect over MCP, read what Periskopos sees, and can only ask to run an action: you approve each one.
Where to go next
Section titled “Where to go next”- Getting started: install it, add an app, connect an account.
- Providers: every account it can read, and the key each needs.
- Connecting an assistant: let Claude or another tool ask it questions.
- Security model: what it protects against, and what it doesn’t.
The name is coined from the Greek peri (around) and skopos (lookout): the one who keeps watch all around. Nova-Shop, Moon-Base and the other apps in these pages are made up.