Blog

Cloud, security and FinOps blog

Practical notes on cloud architecture, security and FinOps, and what we learn building LineXa Studio: what works, what breaks, and how to keep it simple for developers.

Who owns this? Finding the owner of a cloud resource nobody claims A disk, a VM or a database with no owner label cannot be reviewed or deleted. Six signals that point to the owner, and a simple routine to settle it. Read the post →
What can a read-only cloud scan see, and what can it never touch? Before you let any tool into your cloud, ask what it can read, change and keep. What a read-only scan sees, what stays closed, and how to review it. Read the post → Six JQL queries to find dead tickets in your Jira backlog Copy-ready JQL for stale Jira issues: frozen, stuck in progress, wont-do labels, carried-over and empty tickets, and where a plain filter falls short. Read the post → Blueprint: three questions to a whole cloud architecture A blank canvas is the hardest part of designing a cloud app. How LineXa Studio Blueprint turns three answers into components, wiring and a monthly cost. Read the post → OpenSSH CVE-2026-123158 (sshole): password bypass on Alpine OpenSSH before 10.6p2 on musl systems such as Alpine can let a very long password log in to accounts with no password. CVSS 8.1: who is hit and how to fix it. Read the post → How to delete cloud resources without breaking production Nobody dares to delete anything in the cloud. A six-step routine proves a resource is unused, takes a snapshot, quarantines it, and only then removes it. Read the post → Nine zombie resources hiding in your Google Cloud bill Idle disks, snapshots, VMs, IPs and databases quietly add to your Google Cloud bill. Nine zombie resources, how to spot each one, and the evidence you need. Read the post →

See it for yourself.

Everything we write about here is running in LineXa Studio today.