Voice to Text for Cloud Architects
You spend half your day explaining infrastructure decisions in documents, not building infrastructure. Blurt lets you dictate architecture docs, RFCs, and design rationales while your hands stay on your diagrams. Hold a button, describe your multi-region failover strategy, release. Text appears in Confluence, Notion, or wherever your cursor is. No context switching between thinking about systems and typing about systems. Just talk through your architecture like you would to a colleague.
The Typing Problem
Writing architecture decision records after the fact
You made three critical infrastructure decisions during a two-hour design session. Now you need to write ADRs explaining each one. Your whiteboard is full of boxes and arrows, but translating that visual thinking into structured prose feels like a different job entirely. By the time you finish the first ADR, you've forgotten the nuances of the third decision.
Documenting AWS, GCP, or Azure configurations
You just spent an hour configuring a complex VPC with custom route tables, NAT gateways, and security groups. Now you need to document it for the team. You could explain the whole thing in 3 minutes out loud, but typing it into the runbook takes 20 minutes. So you write 'see AWS console' and move on. Six months later, nobody remembers why the config looks the way it does.
RFC writing that blocks other work
The RFC is due by end of week. You know exactly what you want to propose — you've been thinking about this migration strategy for weeks. But translating that mental model into a formal document means hours of typing. You keep pushing it to tomorrow. Meanwhile, the team is blocked waiting for your technical direction.
Responding to architecture review comments
Someone left detailed questions on your design doc in Confluence. You know the answers immediately — this is your area of expertise. But typing out thoughtful responses to eight different comments means an hour of context switching between the doc and your mental model. Your fingers can't keep up with your brain.
Explaining trade-offs in Slack or Teams
A developer asks why you chose DynamoDB over Aurora for this service. You could write a paragraph explaining the read patterns, cost implications, and scaling considerations. Or you could type 'DynamoDB scales better for this use case' and hope nobody asks follow-up questions. Deep knowledge stays in your head because typing it out takes too long.
How It Works
Blurt works in every tool cloud architects use — Confluence, Notion, Lucidchart, Draw.io, Slack, and your cloud console documentation fields.
Hold your hotkey
Press your chosen shortcut. A small indicator shows Blurt is listening.
Talk through your architecture
Explain your design decision, configuration rationale, or RFC section naturally.
Release and done
Text appears at your cursor. No copying, no pasting, no reformatting.
Real Scenarios
Dictating architecture decision records
You just finished a design session where you chose event-driven over request-response for the new order service. Open your ADR template, hold the button, and explain: 'We chose event-driven architecture because order processing is inherently asynchronous. Customers don't need immediate confirmation of fulfillment status. This also decouples the order service from inventory and shipping, letting each scale independently.' Three paragraphs documented in 30 seconds while the decision is fresh.
Writing RFC sections on complex migrations
The database migration RFC needs a detailed rollback strategy. You've thought through every edge case. Hold your hotkey and walk through it: 'If replication lag exceeds 30 seconds during cutover, we abort and fail back to the primary Aurora cluster. Application servers will detect the DNS change within 60 seconds due to the low TTL we set in phase one.' Your mental model becomes documentation in real-time.
Documenting cloud infrastructure configurations
You just set up a Transit Gateway connecting three VPCs across regions. Before you forget the routing decisions, hold the button: 'Traffic between production VPCs routes through the Transit Gateway in us-east-1. The DR VPC in us-west-2 only receives traffic during failover events. We blackhole traffic to the development VPC to prevent accidental cross-environment access.' Your future self and your team will thank you.
Responding to design review feedback
The principal engineer left six questions on your system design doc. You know all the answers but dread typing them. For each comment, hold your button and respond naturally: 'Good catch on the connection pooling. I sized the pool at 20 connections per instance based on our P99 query times and expected concurrency. See the capacity planning section for the full calculation.' Six responses done in 5 minutes, not 30.
Explaining infrastructure trade-offs in Slack
A developer asks why you're recommending EKS over ECS for this workload. Instead of typing a short non-answer, hold the button and give the real explanation: 'EKS gives us portability if we ever need multi-cloud. The team also has more Kubernetes experience than ECS. The additional operational overhead is worth it for the ecosystem of tools we can leverage.' Knowledge shared, context preserved, typed in 10 seconds.
Writing runbook procedures
The on-call runbook needs steps for handling a database failover. You've done this manually a dozen times. Hold your button and walk through it: 'First, check replication status in RDS console. If replica lag is under 10 seconds, initiate failover via the Actions menu. Monitor the events log for promotion completion, typically 60 to 90 seconds. Update the application config to point to the new primary endpoint.' Step-by-step docs written while you remember the details.
Adding context to infrastructure diagrams
Your Lucidchart diagram shows the data flow, but the boxes need explanatory text. Click on the Lambda function, hold your button: 'Validates incoming webhook payloads, extracts order IDs, and publishes to the OrderCreated SNS topic. Timeout set to 30 seconds for slow upstream APIs.' Each component documented in seconds, not minutes.
Why cloud architects choose Blurt over built-in dictation
| Blurt | macOS Dictation | |
|---|---|---|
| Activation | Single hotkey, instant start | Click microphone icon or 'Hey Siri' |
| Speed | Text appears in under 500ms | 2-3 second delay before transcription |
| Technical vocabulary | Handles AWS, GCP, Azure terms accurately | Struggles with VPC, EKS, IAM, and cloud jargon |
| Reliability | Consistent accuracy across sessions | Often fails silently or mishears |
| Documentation workflow | Works in Confluence, Notion, any browser field | Inconsistent in web applications |
Frequently Asked Questions
Start Typing Faster Today
Free to try — no credit card required
Download Blurt