[Brand] Define syner.app Landing Page Messaging & Structure #34
Description
[Brand] Define syner.app Landing Page Messaging & Structure
Area
Brand · Identity · Narrative · Web
Priority
High — Foundational for Syner OS
Objective
Define what the syner.app landing page must communicate, establishing a clear, coherent, and differentiated narrative for an agentic and semantic operating system that is open source, not a SaaS, and has no pricing.
The outcome should serve as the foundation for visual design, final copy, and site structure, aligned with Syner OS positioning.
Strategic Context
Syner is not a SaaS product or an isolated tool.
It's an agentic operating system, composed of multiple domains with well-defined roles:
| Domain | Role | Analogy |
|---|---|---|
| syner.app | Visual interface / OS experience | Windows, macOS |
| syner.dev | Developer resources (SDKs, APIs, protocols, docs) | developer.apple.com |
| syner.run | Execution, usage, and internal billing | Out of scope for this landing |
Important: syner.app does not explain pricing, does not sell features, does not act like a SaaS.
What the Landing Must NOT Be
The syner.app landing must not:
- Look like a SaaS landing page
- Mention "pricing", "plans", or "free trials"
- Use generic AI language ("AI-powered", "boost productivity")
- Sell features or integrations
- Function as a dashboard or traditional marketing funnel
What It MUST Communicate
1. Syner.app is an Operating System, Not an App
The landing must clearly position Syner as:
An agentic and semantic operating system, not a tool.
Key concepts:
- OS > App
- System > Product
- Environment > Service
2. Agents as System Primitives
Syner introduces a new paradigm:
- Agents are first-class entities
- They don't run "in the background"
- They are an active part of the interface
- They have state, memory, and execution capabilities
Suggested narrative:
In Syner, agents are the interface.
3. Human Supervision as a Core Principle
Syner does not propose autonomy without control.
It must be clear that:
- The human supervises
- The agents execute
- Control is intentional, not micromanagement
Key concept:
Supervised autonomy.
4. Paradigm Shift: From Apps to Intent
The landing must convey the conceptual break:
- Traditional systems → apps, clicks, windows
- Syner → intent, context, execution
Core idea:
You don't open apps.
You describe outcomes.
Agents handle the rest.
5. Open Source Without Commercial Confusion
It must be clear that:
- Syner OS is open source
- There is no pricing to use the OS
- Execution and usage are handled outside the scope of this landing (syner.run)
The message must:
- Build trust
- Avoid confusion with "free" SaaS models
6. Who It's For (Without Saying "Users")
Syner is oriented toward:
- Builders
- Engineers
- Operators
- People who build systems
Suggested narrative:
Syner is for those who build systems, not just use them.
Suggested Conceptual Structure
The team can use this structure as a guide:
1. Hero
- Syner as an agentic OS
- Agents + human supervision
- Open source
2. Redefining the OS
- Why current operating systems don't work for agents
3. What is syner.app
- The visual interface of the OS
- Analogy with Windows / macOS
4. Agents as UI Primitives
5. Supervised Autonomy
6. Open Source + Clear Separation from Execution
7. Non-Commercial Call to Action
- "Enter the OS"
- "Explore the interface"
- "View on GitHub"
Visual References (Conceptual)
The design should evoke:
- Modern operating systems
- Dark / minimalist interfaces
- A sense of "desktop", not "web app"
Mental references:
- macOS
- Windows
- Futuristic OS environments
- UI as space, not as form
Tone Guidelines
| Do | Don't |
|---|---|
| OS-first, agent-first messaging | SaaS marketing language |
| Aspirational, clean, benefit-focused | Technical jargon, code examples |
| "Works for you" messaging | "Build agents with SDK" messaging |
| Emotional connection to the paradigm shift | Feature lists and integrations |
| UI as workspace, as space | UI as funnel, as form |
Final Note
This landing does not seek conversion, it seeks comprehension.
If the visitor understands that:
Syner is an operating system for agents, and I am the supervisor
→ the objective is achieved.
Appendix: Operational Details
Ecosystem Reference
| Domain | Purpose | Contains |
|---|---|---|
| syner.app | Public face of the OS | This landing |
| syner.dev | Developer resources | SDK docs, API reference, Protocol spec, Technical architecture |
| syner.run | Business layer | Pricing, Enterprise features, Managed execution |
Out of Scope for syner.app
| Content | Where it belongs |
|---|---|
| SDK documentation | syner.dev |
| API reference | syner.dev |
| Protocol specification | syner.dev |
| Pricing | syner.run |
| Enterprise features | syner.run |
| Technical architecture | syner.dev |
Deliverables
- Main narrative for the landing (syner.app)
- Key messages (headlines + subheadlines)
- Semantic structure of the page
- Tone guidelines (OS-first, agent-first, non-SaaS)
- Visual direction aligned to "agentic OS"
- Responsive layout specifications
- Asset requirements (illustrations, screenshots, videos)
Questions for the Team
- Do we have product screenshots/UI to feature?
- Is a video demo available or needed?
- Are brand colors and typography finalized?
- Is an illustration style defined?
References for Inspiration
- apple.com/macos — Product storytelling, clean design
- windows.com — Productivity focus, feature highlights
- linear.app — Modern aesthetic (but we're NOT SaaS)
- arc.net — Fresh take on familiar software category
Labels: brand, design, landing-page, syner.app