1/4 · I look after a lot of domains, and I wanted to see what needed attention without the monitoring dashboard becoming another job.
ASE brings uptime, DNS and SSL checks together and sends email alerts when something needs a look. It's a focused PHP-backed tool, and the code is MIT-licensed, so you can host it and adapt it to your own setup. Having uptime, DNS and SSL checks in one place means an expiring certificate or a changed record is easier to notice. I wanted fewer tabs to open before deciding what deserves attention.
For me, ownership means being able to understand a check, change an alert and hand the system to the next person without a mystery subscription holding it together. An alert should tell someone what to inspect, not just prove that a dashboard exists.
It has limits too: a compromised server can't be trusted to report honestly about itself. This is day two of the Weekathon, and I'd rather sharpen the useful signals than keep adding dashboard furniture.
Which alert would save you time, and which would you mute within a day?
ASE checks uptime, DNS and SSL and can send email alerts. The front end is backed by PHP for server-side checks and persistence. My aim is a view you can understand quickly enough to act on.
The code is MIT-licensed. You can adapt it to your own domain estate, extend it or commercialise it while keeping the required notices. Hosting, alert delivery and the response process remain your responsibility.
The security boundary matters: ASE assumes an honest server on a hostile network. It is not a defence against an already-compromised host.
For me, the hacker spirit here is curiosity turned into a useful warning. An alert should tell another person what to inspect, not just prove I can make a dashboard. Shared troubleshooting knowledge is part of the delivery.
This is the second product in my Weekathon, seven free and open-source launches in seven days. Junk yesterday was deliberately tiny; ASE raises a different question: can a tool be understandable not just to the person who built it, but to the next person responsible for keeping it running?
The company version of this problem isn't “give everyone AI and ask them to monitor things.” It is one shared workflow with reliable signals, a budget and an owner. A CHO can work with the operations team to build it and document the handoff. Predictable checks belong in code; any model-generated explanation should earn its extra cost. An owned tool may replace a narrow subscription, but server upkeep, alert delivery and incident response still count. This is a way to evaluate the choice, not a measured savings claim.
CHO (Chief Hacking Officer) is a deliberately playful name for a serious role: I'm open to a CHO brief of up to 30h/week with a great company or startup, a worthwhile product, trust and a modest budget. Job offers: paulfleury.com/contact
I'd like reports about missed signals, noisy alerts and checks whose meaning is unclear. Pick a concrete case; I'll assess the useful change and its cost before widening scope.
If you want to contribute with AI, have it trace one check end to end, propose a fix and test the failure path. Review the patch and send a focused PR rather than a rewritten dashboard.
What does a domain-health alert need to tell you before you can act?
I'm at Web Summit in Lisbon today (it runs Mon 9 – Thu 12 Nov) while shipping this. This Weekathon is also dedicated to Web Summit and to the builders' mentality: shipping small, useful things in public, every day, during the week the builders come to Lisbon. If you're around and fancy meeting for a chat about this or anything else, today or later in Lisbon, find me on X (@paulfxyz).
Two other things: Enki (enki.ngo) is a public-good, local-first AI initiative with open blueprints, and I'm looking for people who'd like to help it get started. Openline (openline.com, multi-supplier travel eSIMs) is my main startup, and I'm raising funds to reshape the eSIM market, with a deep pipeline of ideas ready to execute. Angels and VCs can DM me or write via paulfleury.com/contact
Replies
1/4 · I look after a lot of domains, and I wanted to see what needed attention without the monitoring dashboard becoming another job.
ASE brings uptime, DNS and SSL checks together and sends email alerts when something needs a look. It's a focused PHP-backed tool, and the code is MIT-licensed, so you can host it and adapt it to your own setup. Having uptime, DNS and SSL checks in one place means an expiring certificate or a changed record is easier to notice. I wanted fewer tabs to open before deciding what deserves attention.
For me, ownership means being able to understand a check, change an alert and hand the system to the next person without a mystery subscription holding it together. An alert should tell someone what to inspect, not just prove that a dashboard exists.
It has limits too: a compromised server can't be trusted to report honestly about itself. This is day two of the Weekathon, and I'd rather sharpen the useful signals than keep adding dashboard furniture.
Which alert would save you time, and which would you mute within a day?
2/4 · Setup and security boundary
ASE checks uptime, DNS and SSL and can send email alerts. The front end is backed by PHP for server-side checks and persistence. My aim is a view you can understand quickly enough to act on.
The code is MIT-licensed. You can adapt it to your own domain estate, extend it or commercialise it while keeping the required notices. Hosting, alert delivery and the response process remain your responsibility.
The security boundary matters: ASE assumes an honest server on a hostile network. It is not a defence against an already-compromised host.
Try it: https://ase.so
Source: https://github.com/paulfxyz/ase
Other launch days: https://ph.paulfleury.com/
3/4 · A monitor the next operator can understand
For me, the hacker spirit here is curiosity turned into a useful warning. An alert should tell another person what to inspect, not just prove I can make a dashboard. Shared troubleshooting knowledge is part of the delivery.
This is the second product in my Weekathon, seven free and open-source launches in seven days. Junk yesterday was deliberately tiny; ASE raises a different question: can a tool be understandable not just to the person who built it, but to the next person responsible for keeping it running?
The company version of this problem isn't “give everyone AI and ask them to monitor things.” It is one shared workflow with reliable signals, a budget and an owner. A CHO can work with the operations team to build it and document the handoff. Predictable checks belong in code; any model-generated explanation should earn its extra cost. An owned tool may replace a narrow subscription, but server upkeep, alert delivery and incident response still count. This is a way to evaluate the choice, not a measured savings claim.
CHO (Chief Hacking Officer) is a deliberately playful name for a serious role: I'm open to a CHO brief of up to 30h/week with a great company or startup, a worthwhile product, trust and a modest budget. Job offers: paulfleury.com/contact
4/4 · Useful reports and focused contributions
I'd like reports about missed signals, noisy alerts and checks whose meaning is unclear. Pick a concrete case; I'll assess the useful change and its cost before widening scope.
If you want to contribute with AI, have it trace one check end to end, propose a fix and test the failure path. Review the patch and send a focused PR rather than a rewritten dashboard.
What does a domain-health alert need to tell you before you can act?
I'm at Web Summit in Lisbon today (it runs Mon 9 – Thu 12 Nov) while shipping this. This Weekathon is also dedicated to Web Summit and to the builders' mentality: shipping small, useful things in public, every day, during the week the builders come to Lisbon. If you're around and fancy meeting for a chat about this or anything else, today or later in Lisbon, find me on X (@paulfxyz).
Two other things: Enki (enki.ngo) is a public-good, local-first AI initiative with open blueprints, and I'm looking for people who'd like to help it get started. Openline (openline.com, multi-supplier travel eSIMs) is my main startup, and I'm raising funds to reshape the eSIM market, with a deep pipeline of ideas ready to execute. Angels and VCs can DM me or write via paulfleury.com/contact