Keep apps safe

How kanman checks every app before it goes live, keeps keys out of the code, holds each viewer to their own rights, limits what an app can reach, and keeps versions you can roll back with their data.

Building a small app is easy now. Keeping it safe, owned and working a month later is the hard part, and that is my job.

The check before live

Every app, whether I built it or you shipped it, goes through my check before anyone else opens it, and again each time it moves to a wider sharing level. The bar shows the result as kanman’s check: Checking, Questions open, Ready, Live or Blocked.

I look for What happens
Keys or tokens in the code No app is stored or published with a key in its files. I offer to move it to the team’s secrets, or to use a connection your team already has.
Outbound calls Every host the app calls becomes a rule: host, port and purpose. You allow or block each one.
Routes outsiders call Webhooks and other incoming routes become rules too, allowed one by one.
Data your rules keep apart If the app combines sources your team’s rules keep apart, you drop one or ask a lead.
A SQLite file I offer to take it over: its own volume, backups, restore.
Reads another app’s data Not possible: each app reaches only its own data store.
Personal data Flagged in the app’s own data store before it is shared more widely.
Dependencies worth a look Named, with the reason.
Accessibility Gaps on the app’s pages, with what to fix.

Where your risk tiers ask for it, a lead approves with Approve as lead. I never change code or data without a yes.

Rights and reach

  • Each viewer’s own rights. Data from your connections reaches an app only through kanman, with the rights of the person looking. Nobody sees more through a shared app than they could see in kanman.
  • Its own isolated frame. Every app runs separated from kanman, with no access to your kanman session.
  • Only the hosts you allowed. The rules for outgoing and incoming calls are enforced by the network on your runner, not by asking the app nicely. Anything not listed is blocked.
  • Secrets stay outside the code. Set them in the app under Settings > Environment and secrets. They reach the app when it starts, never in its files, and a secret’s value is never shown again after saving. See How team apps are hosted.
  • Your network. Apps run only on your team’s runners. How people’s browsers reach them, through kanman or directly, is IT’s choice: Let people reach apps directly. How apps are isolated, kept up to date and scanned: How team apps are hosted.

Versions and rollback

Every change is a version: a change I make, a new upload from Claude Code, a merge in the app’s repository. They sit on one line at the foot of the app’s window; Restore brings an older one back after one confirm. Code and data go back together. Before every change to how an app stores its data, I back the data up first.

Data that lasts

An app’s own data store lives on your team’s runner and is backed up regularly. With several runners, IT can set a shared folder for backups, so another runner can take an app over when its runner goes away. Without one, the app waits for its runner rather than starting somewhere else with different data, and the owner hears about it. Details for IT: Let people reach apps directly.

When an app breaks

Every app has an owner, and I watch it like any service the team runs. When a source an app reads changes (a renamed field, a removed job), the app says “This app stopped working” and names what changed, and its owner hears about it before someone has to report it. In the catalogue, every app shows whether it is running.

Last updated: January 1, 0001

Open kanman