@Seentyhq Developer | Docker | JavaScript | MongoDB | PHP
Raleigh, NC
- Tweets 321
- Following 76
- Followers 16
- Likes 36
A vulnerability report is useful only when an engineer knows what to fix next. Seenty connects repository scans to clear findings by severity, file, and dependency. Start free: seenty.com/?v=2
4
During an incident, the hidden cost is context switching: alert in one tool, logs in another, traces somewhere else. That fragmentation is why I’m building Seenty. Try the free plan: seenty.com/?v=2
8
A domain can be online while SSL, DNS, exposed services, or forgotten subdomains create risk. I built Seenty to bring those signals into one view. Create a free account and scan yours: seenty.com/?v=2
15
If I could improve one thing before Monday, it would be the path from 'something is wrong' to 'here is the context.'
That is a big part of why I am building Seenty.
Where does your team lose time during diagnosis?
seenty.com/?v=2
9
A runbook test I like: could someone outside the team follow the first five minutes?
Clear ownership matters as much as tooling. We bring on-call and incidents together in Seenty.
What makes your runbooks usable?
seenty.com/?v=2
8
Friday thought: a certificate expiry has a date. It should not become a surprise.
Seenty includes SSL expiry monitoring alongside uptime checks.
What predictable failure would you automate out of your week?
seenty.com/?v=2
5
I like incident updates that answer 3 things:
1. What is affected?
2. What are we doing?
3. When is the next update?
Seenty status pages help keep customers informed.
What would you add?
seenty.com/?v=2
6
My cloud security starting point: who can access what, and what is exposed?
Seenty brings AWS and Azure posture checks alongside monitoring.
Which is harder on your team: finding a misconfiguration or getting it fixed?
seenty.com/?v=2
32
An HTTP 200 is a clue, not the whole customer experience.
I want to know where a check ran and what it actually verified. Seenty supports regional and keyword checks.
What do you check beyond status codes?
seenty.com/?v=2
12
My test for a useful dashboard: does it help me decide what to do next?
That is how I think about building Seenty: monitoring, security and incident context in one place.
What makes a dashboard worth keeping open?
seenty.com/?v=2
8
17 tools. $1,000/mo. Seenty starts free. 💸
Monitoring, security and incident response, unified in one dashboard, no credit card needed to try it.
What's your current stack actually costing you?
seenty.com/?v=2
13
An API key hardcoded 18 months ago is still a live key today. 🔑
Nobody rotates a secret they forgot they committed. It sits in git history, working, until someone finds it who shouldn't.
When did you last scan your own repo history?
seenty.com/?v=2
16
What does "normal" look like on your systems? 🤔
Not the SLA. The actual shape of a Tuesday.
You cannot spot an anomaly if nobody agreed what the baseline was.
How long before your team agrees something is wrong?
seenty.com/?v=2
1
23
Ask your team to list every domain the company owns. 🌐
You will get most of them.
The gap is where the trouble lives. A campaign site from three years ago. A subdomain a contractor set up.
How many would you miss?
seenty.com/?v=2
13
"How was uptime last month?" 📅
The honest answer for most teams: give me an afternoon.
You build that report once, for a board deck, then never again until someone asks. So nobody asks.
Could you answer it today?
seenty.com/?v=2
12
A dashboard has one job. ⏱️
Let you look for five seconds and know whether today is normal.
If it takes longer, it is not a dashboard, it is a report. Reports are fine. They are just not what you want at 3am.
Does yours pass the five second test?
32
The cert did not expire suddenly. 🔐
It expired on a date known 90 days ahead. Nobody was watching the schedule.
The postmortem says "certificate expiration." The cause is that the date lived in an inbox.
Who owns renewal on your team?
seenty.com/?v=2
12
CPU at 3%. Every request failing. 🧵
Connections never get released, max_connections is reached, and the database refuses everyone while looking completely idle.
From the app side it is an outage. From the database side nothing is wrong.
Ever lost a night to this?
1
1
20
Your uptime monitor checks HTTP. What breaks you does not always speak HTTP. 🚪
The database port. The queue. The internal service everything depends on.
All green, still down.
Least monitored thing in your stack?
seenty.com/?v=2
1
1
28
