rvzd

I build software in my own time. Right now that’s anypocket, a browser extension that saves pages to Anytype, and rvzd monitor, a monitor for the servers I run.

anypocket

Released, version 1.1.1

Save the page you’re reading to Anytype as a bookmark, with a note on why you kept it.

Open it from the toolbar or with Option + Shift + S, check the preview, pick a space, add a note and save. Everything goes straight to Anytype Desktop on your own computer.

No account, no server and no analytics. Available in English, Russian, German, French and Spanish.

Browsers
Firefox 142+, Chrome, Edge, Brave
Needs
Anytype Desktop running on the same computer
Price
Free

Get anypocket

The anypocket popup: a preview of the page, the chosen Anytype space, a note field and a Save to Anytype button. The anypocket popup: a preview of the page, the chosen Anytype space, a note field and a Save to Anytype button.

rvzd monitor

Private, in development

A small agent on each server reports to one hub, which keeps the metrics and opens an incident when something breaks.

An optional assistant looks into each incident with read-only tools: logs, metrics, services, network checks. It can propose a fix, but nothing runs until I approve it, and it comes back later to check that the fix held.

Not public yet. It runs my own machines while it grows up.

Built with
Go, WebSocket, React
Parts
Hub, agents, web dashboard

See how it works

web-1 online degraded up 148d
Memory
HTTP, shop.example.com no response

Down since 14:02, from all three servers

  1. warningsystem

    Network check: 3 of 18 failed

    networknetcheck14:02

  2. criticalsystem

    Incident #92 opened: postgresql.service failed web-1

    incident14:02

  3. infoAI

    AI picked up incident #92

    AI action14:03

  4. infoAI

    AI analysis: reading logs AI analysis: postgres was killed by the OOM killer

    memory is back to 20%14:03

  5. warningAI

    Proposal #57: restart postgresql.service

    needs younothing runs until approved

Proposal #57 low risk web-1

Why: postgres was killed by the OOM killer at 14:01 while a report query ran. The query is gone and memory is back to 20%, so a restart should hold.

  1. 1reset_failedpostgresql.service
  2. 2restart_servicepostgresql.service

Waiting for you. The assistant can’t run this itself.

rvzd | alerts 14:04

AI proposal #57 on web-1: reset_failed, restart_service postgresql.service. Approve or reject in the dashboard.

Proposal #57 web-1 Reject Approve Approved
  1. ✓ reset_failed postgresql.service 0.2 s
  2. ✓ restart_service postgresql.service 1.6 s

active postgresql.service is running again. Checking that it holds.

Verification AI incident open resolved
sleep 30s get_service_status postgresql get_service_logs postgresql, 1m

postgres has been up for 40 s and is accepting connections, and its log has been clean since the restart. Resolved.

judgea second model grades the answer

  • resolved 0.92
  • still broken 0.05
  • needs a human 0.02
  • false alarm 0.01

Claims it ran something itself: no, 0.01