# voice.md

## Communication Style

### Overall Tone and Personality
Fly.io's brand voice is **confident, opinionated, and technically sophisticated**, yet distinctly **informal and approachable**. It's the voice of a seasoned developer speaking to peers – direct, empowering, and occasionally irreverent. We empower developers to build "fearlessly" and "just ship," while maintaining a clear, expert stance on complex technical topics. There's a subtle, dry humor and a willingness to be blunt, which builds trust and authenticity with our audience.

### Key Stylistic Elements and Patterns
*   **Direct and Active:** We use active voice and address the reader directly ("you," "your app"). Our language is action-oriented and impactful.
*   **Technical Depth with Clarity:** We don't shy away from complex technical terms, but we strive to explain them clearly, often using relatable analogies and metaphors ("Again with the sandwiches," "It’s like boiling water").
*   **Empowering Language:** Words and phrases that convey capability, freedom, and ease are central ("superpower," "fearlessly," "without complexity," "get out of your way").
*   **Concise and Punchy:** Especially in headlines and marketing copy, we favor short, impactful sentences and phrases.
*   **Authentic and Conversational:** We incorporate parenthetical asides, rhetorical questions, and occasional strong language (when appropriate and authentic to the context, like in a blog post about a security incident) to create a conversational feel.
*   **Problem/Solution Framing:** We often frame our content around common developer challenges and present Fly.io as the elegant solution.

### Vocabulary Preferences and Word Choices
*   **Developer-Centric:** We use terms familiar to our audience: `compute`, `sandboxes`, `agents`, `VMs`, `containers`, `deploy`, `runtime`, `pipelines`, `CLI`, `frameworks`, `object storage`.
*   **Impactful & Benefit-Oriented:** `fearlessly`, `superpower`, `instantly`, `confidence`, `scalable`, `persistent`, `ephemeral`, `modern`, `robust`.
*   **Direct & Unflinching:** `unfortunately`, `here goes`, `no problem`, `for fuck's sake` (used sparingly and contextually).
*   **Brand-Specific:** `Machines`, `Sprites`, `Phoenix.new`, `Litestream`.

## Content Patterns

### Common Themes and Topics
*   **Developer Empowerment:** Enabling developers to build, ship, and scale their applications with ease and confidence.
*   **Performance & Scalability:** Global distribution, low-latency, instant launches, and handling high loads.
*   **Security & Isolation:** Emphasizing hardware-virtualized containers, isolated sandboxes, and secure environments.
*   **AI/ML Applications:** Running agents, LLMs, and model evaluation.
*   **Specific Technologies:** Deep dives into frameworks (Rails, Phoenix, Django), databases (SQLite, Postgres), and infrastructure concepts.
*   **Problem Solving:** Addressing common pains in deployment, scaling, and managing distributed systems.

### Structural Approaches to Content
*   **Blog Posts:** Often begin with an engaging, sometimes provocative title. They typically lead with a narrative hook or a direct statement of the problem, followed by detailed technical explanations, solutions, and often personal insights or opinions. They conclude with an implicit or explicit call to action.
*   **Marketing Copy:** Follows a clear hierarchy: strong headline -> concise value proposition -> feature highlights (often with sub-headlines and bullet points) -> specific use cases -> social proof -> enterprise capabilities -> overarching vision and clear call to action.

### Call-to-Action Styles and Patterns
Our CTAs are direct, action-oriented, and focused on getting the user to experience the product.
*   **Direct & Imperative:** "Deploy your app," "Get Started," "Spin Up a Sandbox," "Build for scale from Day One."
*   **Benefit-Driven:** "Check Em Out!", "Learn More."
*   **Often links to sign-up, documentation, or specific product pages.**

## Audience Interaction

### How the Brand Addresses Its Audience
We address our audience directly as "you" – the intelligent, capable developer or builder. We assume a level of technical understanding and aim to be a trusted peer and enabler, not a lecturer. We speak to developers' aspirations and challenges, positioning Fly.io as the solution that "gets out of your way."

### Level of Formality and Relationship Style
The relationship is **informal but professional**, **peer-to-peer**. We are experts who understand the developer's world and speak their language. We avoid overly corporate jargon, favoring a more authentic, conversational, and occasionally witty tone that fosters a sense of camaraderie.

### Engagement and Conversation Patterns
*   **Rhetorical Questions:** Used to engage the reader and anticipate their needs or thoughts ("No Dockerfile? No problem").
*   **Shared Experience:** Acknowledging common challenges or even internal missteps builds rapport ("We know. Our Twitter got owned.").
*   **Encouraging Exploration:** Our content often inspires readers to try things out, experiment, and build.

## Guidelines & Examples

### Do's and Don'ts for Brand Communication

**DO:**
*   Be direct, confident, and technically precise.
*   Use active voice and strong, evocative language.
*   Embrace a slightly irreverent, informal, or witty tone where appropriate, especially in blog posts.
*   Focus on developer benefits, empowerment, and efficiency.
*   Use metaphors and analogies to simplify complex technical concepts.
*   Address the reader as an intelligent, capable peer.
*   Highlight speed, scalability, security, and ease of use.
*   Be authentic and transparent.

**DON'T:**
*   Be overly formal, corporate, or generic.
*   Talk down to the audience or oversimplify to the point of inaccuracy.
*   Use excessive passive voice or bland, uninspired language.
*   Sound like a marketing brochure when the content calls for technical depth.
*   Avoid strong opinions or a distinct personality.

### Example Phrases and Expressions That Are "On-Brand"
*   "Build fast. Run any code _fearlessly._"
*   "The platform for devs who just want to ship."
*   "Sandboxes That Feel Like a Superpower."
*   "Forget wrestling with shared runtimes or noisy neighbors."
*   "No Terraform required."
*   "It’s like boiling water."
*   "The future isn't model agnostic."
*   "for fuck’s sake." (Use with extreme caution and only in appropriate, informal contexts like a blog post about a security incident).
*   "Getting the spe[ed]..." (Playful, incomplete phrases).

### Content Types and Formats the Brand Uses
*   **Technical Blog Posts:** Deep dives, announcements, opinion pieces, tutorials, incident reports.
*   **Marketing Landing Pages:** Benefit-driven overviews, feature highlights, product descriptions.
*   **Product Documentation:** Comprehensive guides and references.
*   **Customer Stories:** Showcasing how others use Fly.io.
*   **Community Interactions:** Forums, social media (implied).