# voice.md

## Communication Style

### Overall Tone and Personality
Fly.io's voice is **confident, highly technical, and unapologetically direct**, yet infused with a **conversational, often witty, and sometimes irreverent** personality. We speak like fellow developers who understand the frustrations and aspirations of building and shipping code. Our tone is authoritative without being arrogant, knowledgeable without being inaccessible. We empower developers by cutting through complexity and speaking plainly about powerful solutions.

### Key Stylistic Elements and Patterns
*   **Direct & Action-Oriented:** We use strong verbs and active voice, focusing on what developers *can do* with Fly.io.
*   **Technical but Accessible:** We embrace technical jargon where appropriate but often clarify complex concepts with relatable analogies, metaphors, or straightforward explanations.
*   **Conversational & Engaging:** We use contractions, direct address ("you"), and occasionally inject humor or blunt honesty to create a personal connection.
*   **Confident & Opinionated:** We're not afraid to state our beliefs about how things should be built or the value of our approach.
*   **Concise yet Informative:** We get to the point quickly, valuing clarity and efficiency in our explanations.
*   **Empathetic to Developer Challenges:** We acknowledge the pain points of modern development and position Fly.io as the solution that "gets out of your way."

### Vocabulary Preferences and Word Choices
*   **Technical Precision:** Terms like "hardware-virtualized containers," "WAL checkpoints," "NVMe," "KVM," "LLMs," "AI agents," "distributed systems."
*   **Empowering Language:** "Fearlessly," "superpower," "ship," "simplify," "unleleash," "build better."
*   **Relatable Analogy:** "Sandwiches," "pen drawer," "boiling water" to explain complex tech.
*   **Authentic & Sometimes Edgy:** We're not afraid of words like "fuck's sake" in appropriate, informal contexts (e.g., blog posts about security incidents) to convey genuine emotion or frustration.

## Content Patterns

### Common Themes and Topics
*   **Developer Empowerment:** Enabling developers to build and deploy any code with ease and confidence.
*   **Performance & Scalability:** Emphasizing speed, low latency, and global distribution.
*   **AI Agents & LLMs:** A significant focus on running, building, and evaluating AI-powered applications.
*   **Distributed Systems & Databases:** Solutions for clustered databases, global Postgres, and robust infrastructure.
*   **Specific Frameworks:** Support for Rails, Phoenix, Django, Node, Laravel, .NET, SvelteKit, NextJS.
*   **Security & Reliability:** Highlighting isolated environments, memory-safe stacks, and enterprise-ready features.

### Structural Approaches to Content
*   **Problem/Solution:** Often starts by outlining a common developer challenge, then introduces Fly.io's feature or product as the elegant solution.
*   **Benefit-Oriented Headings:** Headings clearly state the advantage or capability being discussed (e.g., "Modern Compute Without the Complexity," "Sandboxes That Feel Like a Superpower").
*   **Narrative & Explanatory (Blogs):** Blog posts often tell a story, share an opinion, or dive deep into the implementation details of a feature, using a more informal, conversational flow.
*   **Feature/Benefit Pairings (Marketing):** Product descriptions clearly link features to their direct benefits for the user.

### Call-to-Action Styles and Patterns
*   **Direct & Imperative:** Clear instructions that prompt immediate action.
*   **Benefit-Driven:** CTAs often highlight what the user will gain by clicking.
*   **Product-Specific:** Tailored to the specific product or action being promoted.
*   **Examples:** "Deploy your app," "Check Em Out!", "Learn More," "Build for scale from Day One," "Spin Up a Sandbox," "Get Started."

## Audience Interaction

### How the Brand Addresses Its Audience
We address our audience as intelligent, capable developers who are looking for powerful, straightforward tools. We speak to them as peers, sharing insights and solutions rather than lecturing. We assume a baseline technical understanding but strive to make complex topics digestible.

### Level of Formality and Relationship Style
The relationship is **peer-to-peer and collaborative**. While we are experts providing a service, we position ourselves as partners in the development journey. The level of formality is **informal-to-semi-formal**, leaning more informal in blog posts and community interactions, and slightly more structured in core marketing copy, but always maintaining a human, authentic voice.

### Engagement and Conversation Patterns
We encourage engagement by presenting compelling arguments, offering practical solutions, and sometimes provoking thought. We invite developers to "just ship" and remove obstacles, fostering a sense of shared purpose and efficiency. Our voice is designed to resonate with those who value directness and powerful tools.

## Guidelines & Examples

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

**DO:**
*   **Be direct and confident:** "Build fast. Run any code *fearlessly.*"
*   **Embrace technical depth:** Don't shy away from explaining *how* things work.
*   **Use analogies to simplify:** "It’s like boiling water."
*   **Focus on developer benefits:** "The platform for devs who just want to ship."
*   **Inject personality and wit:** "Kurt Got Got," "For fuck's sake" (contextually appropriate).
*   **Use active voice and strong verbs:** "Deploy," "Run," "Spin up," "Scale."
*   **Be opinionated and passionate:** "The most important storage technology of the last 20 years."

**DON'T:**
*   **Be overly corporate or generic:** Avoid buzzwords that lack substance.
*   **Talk down to developers:** Assume a level of intelligence and experience.
*   **Be vague or ambiguous:** Clarity is paramount.
*   **Over-promise or exaggerate:** Maintain credibility through honesty.
*   **Use passive voice excessively:** Keep language dynamic and impactful.
*   **Be overly formal or stiff:** Our voice is approachable.

### 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."
*   "Modern Compute Without the Complexity."
*   "Get right in your users' faces."
*   "The platform that gets out of your way."
*   "Forget wrestling with shared runtimes or noisy neighbors."
*   "Pay only for actual CPU and memory consumption, down to the second."

### Content Types and Formats the Brand Uses
*   **Technical Blog Posts:** Deep dives, tutorials, opinion pieces, announcements.
*   **Marketing Copy:** Website landing pages, product feature descriptions, ad copy.
*   **Documentation:** Clear, concise, and comprehensive guides.
*   **Customer Stories:** Showcasing real-world applications and success.
*   **Community Interactions:** Forum posts, social media updates.