See what your cloud is doing.
Gildyard draws your Azure subscription as a living yard. Every resource group is a building, every resource a piece. Smoke rises from what fails, cobwebs grow on what sits idle, and a price tag hangs on idle things you still pay for.
Nothing to install. Read-only, by Azure's own rules. You can disconnect at any time. Azure today; AWS and Google Cloud next.
Reading the yard
Failing
Smoke, and a red beacon
Errors in the last hour: a function returning 5xx, a pipeline run that failed, a database refusing connections. Tap the piece and it says how many, and where to look.
Measured from: 5xx responses, failed runs and server errors, from Azure Monitor.
Idle, still billed
Cobwebs, and a price tag
Nothing has happened for weeks, longer than that kind of resource should rest. When Cost Management says it is still billing, the piece gets a price tag with what it has cost so far this month.
Measured from: Thirty days of activity, and this month's cost from Cost Management.
Working
Sparks above it
Something happened in the last hour. Forklifts move when functions run, conveyors turn when messages flow, trucks leave when data moves.
Measured from: Requests, executions, transactions and messages, from Azure Monitor.
Greyed out means stopped or deallocated. A red gauge on a vault means a database above 85% of its capacity.
How it connects
Your Azure
Your subscriptions, as they are. Nothing is installed in them.
Gildyard
Reads, draws, and keeps the latest picture and the recent events.
Your team
Signs in with Microsoft. Sees the yards they're given, nothing else.
What it reads: your resources' names, types, regions, sizes and resource groups; activity numbers such as requests, runs, errors and CPU; and this month's cost per resource. What it never does: change anything, read the data inside a resource, read a secret, or keep a copy of your tags.
Connecting takes one button in the app, or the two commands and the template in the documentation, which also says exactly how to take the access back.
Who it's for
Platform and cloud engineers
Who run a handful of subscriptions and want to see them, not query them.
Engineering leads
Who want the one picture that says whether today is a normal day.
Teams paying for things they forgot
A price tag on an idle piece is hard to ignore.
On your office TV
Every yard can have TV links. A screen in the office shows the yard with no sign-in, the way a status board should, and the link can be switched off from the yard's settings at any time.
Questions
- What does it read?
- Your resources' names, types, regions, sizes and resource groups, from Azure Resource Graph; activity numbers from Azure Monitor, such as requests, runs, errors and CPU; and this month's cost per resource, from Cost Management.
- Can it change anything?
- No. It holds two of Azure's built-in read-only roles, Reader and Cost Management Reader. Neither can change a resource, read the data inside one, or read a secret.
- Who sees our yard?
- Only the people your team's owners and admins add in Gildyard, with the role and the yards they're given. Every change lands in an activity log.
- How current is it?
- New, stopped and deleted resources show within a minute or two. Gildyard reads activity, errors and load from Azure Monitor every five minutes, so they can take up to ten minutes to appear. When Azure has no data for something, the yard leaves it alone instead of guessing.
- What about our tags?
- They arrive with the resource list and are dropped before anything is stored. Tags often hold names and email addresses; Gildyard never keeps them.
- Where does the data live?
- In Azure's Spain Central region, in the EU. A yard keeps only its latest picture and its recent events.
- How do we remove it?
- Disconnect the yard in its settings, which deletes everything Gildyard stored about that subscription, apart from the activity log's record that it was connected and disconnected. Then delete its two role assignments in Azure, and it can't read anything any more.
- What does it cost?
- Nothing during early access. Pricing comes with the paid launch, and early-access teams hear it first.
The long answers, with the exact commands, are in the documentation.
Thanks. You're on the list. We'll write when there's room.
- We read every request and reply from [email protected] within a few days.
- When there's room, you get an invite link for the Microsoft work account you'll sign in with.
- You connect a subscription and your yard appears within minutes.