miakapp

How it works

Miakapp does four things. Your agent does the rest.

Miakapp ships no device integration, no rule engine and no ready-made dashboard. It is a foundation: it hosts your home’s app, signs in the people who live there, sends notifications and keeps working when the internet goes down. The devices, the automations and the interface are built by your agent, for your home and nobody else’s.

The path of a tap

Four pieces, two of them written by your agent. When someone taps a button in the app, the call goes through the relay to the coordinator, which decides whether that person may do it, acts on the device, then publishes the new state every open app shows at once.

  1. At homeThe devices

    Zigbee, MQTT, Wi-Fi, 433 MHz radio, infrared, a manufacturer’s cloud API… it does not matter.

  2. At home · written by the agentThe coordinator

    A TypeScript program running around the clock on a Raspberry Pi or a mini PC. It talks to the devices, holds the home’s state and decides who may do what.

  3. MiakappThe relay

    It connects the coordinator to the people of the home, wherever they are, and keeps the last known state.

  4. On every phone · written by the agentThe home’s app

    A real web application, designed for your home, and for each person in it if needed.

What Miakapp takes care of

1. Hosting the home’s app

The interface is a complete web application: HTML, CSS, JavaScript, whatever libraries the agent finds useful. It bundles it into one file and publishes it with miakapp publish. Miakapp serves it on www.miakapp.com in an isolated frame on a separate origin: it has no network access and no shared storage, and talks to the home only through the window.miakapp bridge. Every publication is versioned and can be undone in one command.

The WebSocket relay connects the pieces. The coordinator opens the connection, outbound: no port to open on your router, no fixed IP address. The relay caches the last published state, so the app opens at once with the last known values and flags the ones that are no longer fresh instead of passing them off as current. It routes every call to the coordinator that declared it.

To be precise: the relay terminates the encrypted connection and sees the state in plain text. This is not end-to-end encryption, and we do not present it as such.

2. Signing people in

Everyone in the home has their own Miakapp account: sign in with Google or with a link sent by email, no password to remember. One person can belong to several homes.

With every call, the relay attaches the person’s verified identity, which the app cannot forge. What they may do is decided by the coordinator, so by the agent, following what you asked: “the kids don’t touch the heating”, “guests can open the gate from 8 am to 8 pm”.

The agent never has your password. You give it access to one home from miakapp.com/pair, with a single-use code valid for ten minutes. It gets its own key, which you can revoke at any time without touching the others.

3. Push notifications

Push notifications on Android, on computers and on iPhone once Miakapp is added to the Home Screen. No app to install from a store. The agent sends them from the coordinator (“the freezer is up to −12 °C”) or with one command, miakapp notify.

4. Working without the internet

If the home’s connection or the relay goes down, the coordinator serves the same app directly on the local network, without the relay or any cloud, behind an access token if needed. The app needs no change: the window.miakapp bridge is the same. Bookmark the local address; it is the one you need the day the router keeps rebooting.

What your agent builds

Everything that makes your home yours, and like no other:

  • Advising on hardware. Preferably local, open protocols (Zigbee, MQTT, Tasmota, ESPHome) that work without the manufacturer’s cloud.
  • Connecting devices, even closed ones. A 433 MHz radio remote, an infrared air conditioner, a cloud app with no public API: the agent finds out how the device communicates and plugs into it.
  • Writing the coordinator. Integrations, automations, each person’s rights, with tests.
  • Designing the interface. One screen for the family, another for the kids, one for the hallway tablet, in whatever style you like.
  • Keeping it moving. You ask, it changes the code, publishes and checks the result in the real app.

Why such a small foundation?

Classic home automation platforms try to anticipate everything: thousands of integrations, a rule editor, dashboard cards. Each of those pieces is also a limit: whatever the editor cannot express, you cannot do. An agent that writes code does not need those crutches. Miakapp keeps only what would be tedious or risky to rebuild in every home: hosting, the identity of the people who live there, notifications and resilience.

What you need

  • A coding agent. A molted.cloud agent, Claude Code, Codex or another one: the @miakapp/cli CLI and its guide are all it needs.
  • A machine that stays on at home for the coordinator: a Raspberry Pi or a mini PC.
  • A Miakapp account, to create the home and invite the people who live there.

Miakapp’s code is public: github.com/Miakapp/Miakapp-V3.

So what do you ask it?

Requests no rule editor can write.

See the ideas Create my home