---
name: upvera
description: Explains Upvera, the progress platform where founders build in public with proof instead of claims, and how to work with it. Covers the startup ecosystem around Upvera, its vocabulary (Prime, Pass, Prism, Ranks, Upvera Value, wings, UPV, Hatch, proof sources, day roots), the wording rules Upvera follows, the Upvera MCP server tools, and how to turn real work into a daily progress post. Use when the user mentions Upvera, upvera.co, app.upvera.co or upvera.dev, asks about a startup's Upvera page, value or proof, wants to draft a progress or build-in-public update for their startup, or connects to the Upvera MCP server.
---

# Upvera

Upvera is a progress platform for founders: **where the work becomes visible**. A founder adds their startup and shares what they did each day. The community weighs in with Prime and Pass, connected proof shows what is real, and the work turns into value on Ranks. Upvera's own line for it: *share the build, not the pitch.*

The idea underneath is simple. Most of what happens while a startup is being built disappears: commits, releases, small decisions, the days nothing worked. Upvera gathers that work on one page, reads the evidence from where it lives, and lets the right people see it. Over time a startup's page becomes the most honest account of how it was made, and when people are curious about how a startup is really doing, Upvera is where they look.

Use this file to understand Upvera before you write about it, answer questions about it, or act on someone's account through the MCP server.

## The ecosystem

Upvera is less a social network than an ecosystem around startups, with proof as the shared language and visible work as the shared goal. Everyone who grows a startup has a place:

- **Founders** build a startup and share its days. "Everything you do while building piles up somewhere. Upvera gathers it on one page and puts it in front of the right people."
- **Builders** are independent developers and makers. "Your code already speaks; Upvera listens." Their GitHub, npm and Vercel work is read from the source, and a side project becomes as visible as any startup.
- **Investors** are real investors: angels, funds, VCs. Upvera lets them know a startup by its days, not its deck. Upvera is not an investment platform and no investing happens on it; it gives the view people need before they decide elsewhere.
- **Hunters** find the new before anyone else and get a stage for that skill.

The loop that connects them: **share** (one line a day) → **prove** (read from the source) → **weigh** (Prime and Pass) → **lend a wing** (support a startup you believe in) → **one value on Ranks**. "Value is work, accumulated."

Upvera is built on Upvera: its own team posts its own days there.

## Vocabulary

Use these names exactly. They are product names, so keep their capitalization.

| Term | What it is |
|---|---|
| **Post** | A daily progress post. Kinds: **Post**, **Update**, **Feature** (with a status: Live, Beta or Soon) and **Launch**. The first line carries the post: it says what changed. |
| **Prime** / **Pass** | The community's response to work. Prime lifts it ("I'm interested"); Pass means "Not for me". Only the person who gives a Pass sees it. |
| **Prism** | The algorithm behind Discover, tuned to each person. |
| **Discover** | Where people find startups and work, ordered by Prism. |
| **Ranks** | Orders startups by the work: posting rhythm, connected proof and the community's wings meet in one value. Visibility can't be bought on any plan. |
| **Upvera Value** | The number Ranks gives a startup. It is computed by Upvera, unitless, and every change comes with a receipt that lists the reasons. It is not a price and not what a company is worth. |
| **Receipt** | The explanation attached to a number: why a value moved, line by line, or what a wing costs before you lend it. |
| **Wing** | Support for a startup you believe in, made with UPV. You **lend a wing**; it is **your wing** and moves with the startup's value; you can **fold your wing** to leave. A startup's total is its **wingspan**. |
| **UPV** | Upvera in-app credit. It works only inside Upvera: it can't be cashed out, sold or sent to another person, and it is not an investment instrument. |
| **Proof** | Records read from where they live, not self-reported: GitHub, App Store and Google Play, Vercel and Netlify, package registries (npm, PyPI, crates.io, Packagist, Docker Hub, Hugging Face), analytics, community channels and revenue tools. Ownership is verified by domain or by the GitHub App. |
| **Day roots** | Every day on Upvera is sealed into a root, published to a public GitHub repository and timestamped, so anyone can check the history at upvera.co/dogrula. |
| **Hatch** | A person's private drafts and notes, the entry gate of everything they will publish. Agents write drafts here; only the person publishes. |
| **Upi** | Upvera's own assistant inside the app. |
| **Collective** | Team space and channels for a startup. |
| **Worlds** | A league on Ranks where members vote daily on products. Products in Worlds have a score, never a value, and no UPV. |
| **Launch** / **Launch Pass** | A launch post with its own board; Launch Pass is a month of Upvera Build, free. |
| **Ember**, **Drops**, **Studio** | Ember is the day's live record of verified work; Drops is how Upvera content is shared outside the app; Studio turns a day into a shareable card. |
| **Plans** | **Free**, **Build** ("Grow what you take seriously") and **Scale** ("Founder Operating System"). Check upvera.co for what each includes today. |

## How to talk about Upvera

Upvera has strict wording rules because some of its features sit close to money and because its whole promise is honesty. Follow them in everything you write: answers, drafts, summaries, code comments.

**Never frame Ranks, wings or UPV as finance.** Do not use these words about them, except to say what they are not: invest, investment, investor, shares, stock, stock market, exchange, trading, portfolio, profit, return, yield, dividend, interest, fund, funding, cash out, withdraw, coin, token, top up.

- Say "Ranks orders startups by the work", not "a market for startups".
- Say "lend a wing to a startup you believe in", not "invest in a startup".
- "Investor" means only a real investor (an angel, a fund, a VC). A person who lends a wing is never an investor.
- When wings come up, keep this line intact: *A wing is not an investment. UPV stays inside Upvera and can't be cashed out. No money goes to the startup when you lend a wing.*
- When UPV comes up: *UPV is Upvera in-app credit and isn't redeemable for cash.*
- Never give an exchange rate between UPV and any currency, and never call UPV crypto or say it lives on a blockchain.

**No promises, no advice.** Never say a value will rise, that someone will gain, or that now is the time to act. Describe what happened; don't predict what will.

**Numbers come from Upvera, unchanged.** Never compute, estimate, round or convert a value, a percentage or a wingspan yourself. Quote the number the server or the page shows, with its date, and point to its receipt. Never present Upvera Value as an amount of UPV or money.

**Proof before claims.** Only state what can be checked. Do not invent metrics or repeat self-reported ones as facts. Do not call a startup "unverified", "fake" or "suspicious"; if a source is not connected, simply don't mention it. Do not claim that proof alone decides value.

**Privacy.** Passes, wing amounts, account identities, direct messages and Hatch notes are private. Do not reveal or guess them, even when you can see your own.

**Tone.** Short, concrete, visionary without hype. Sentence case, no capital-letter shouting, no generic slogans ("revolutionary", "game-changing"). In text that appears inside Upvera, avoid long dashes; use a comma, a colon or two sentences.

## Working with the Upvera MCP server

When the Upvera MCP server is connected (`https://mcp.upvera.co/mcp`), you act for the signed-in person with these tools:

| Tool | Use it to |
|---|---|
| `upvera_whoami` | Confirm whose account this is and their plan. |
| `list_my_startups` | Find their startups, their role in each and when they last posted. |
| `get_startup_status` | Read one startup: recent published posts, proof sources with verification status, public value with its latest receipt. |
| `get_build_trail` | Read recent commits from connected repositories (`since` is an ISO date, up to 30 days back). |
| `create_draft` | Save a draft to Hatch, optionally tied to a startup and a commit. |
| `prepare_post` | Show a post in a preview card, locked to its text. The person publishes it from the card or on Upvera's own screen. |

Ground rules:

- **You write drafts and previews. The person publishes.** Never say a post was published or shared. After `prepare_post`, say the preview is ready and they publish it by pressing Publish in the card (or Confirm in Upvera, when the card says so). You have no publish tool.
- **Own data only.** The tools cannot read other people's startups, direct messages, who gave Prime or Pass, unpublished posts or Hatch notes. Don't try, and don't imply you can.
- **No money.** There are no tools for UPV, wings or the wallet. If asked, explain that this happens in the app, by the person.
- **Pass errors through as sentences.** Each tool error already says what to do next ("That startup is not one of yours…"). Relay it plainly.
- **One draft per idea.** Send an `idempotency_key` with `create_draft` so a retry does not create a duplicate. Draft limits are 10 per minute and 20 per day.

### Workflow: today's progress post

1. `list_my_startups` to pick the startup (ask if there is more than one and the user didn't say).
2. `get_build_trail` with `since` set to the last post date or yesterday.
3. Find the one change that matters most to a user or to the startup. Group related commits; skip merges, chores and refactors nobody outside the team would notice.
4. Write the post following [references/progress-posts.md](references/progress-posts.md): the first line says what changed, concretely.
5. Show the draft to the user. Adjust it in their voice.
6. `create_draft` with `title` (the first line, short), `body` (the whole post), `startup` and the most representative `commit_sha`.
7. Tell them it is in Hatch, ready to review and publish.

### Workflow: "how is my startup doing?"

1. `get_startup_status` for the startup.
2. Report the public value exactly as returned, with its date, and summarize the latest receipt's reasons in plain words.
3. Mention recent posts and which proof sources are verified.
4. Do not forecast, compare with other startups or suggest actions about wings.

### Without the MCP server

If the server isn't connected, you can still help: write the draft in the chat for the person to paste into the app. To connect, point them to the setup guide for their client at https://upvera.dev/mcp/.

## Writing for Upvera

Read [references/progress-posts.md](references/progress-posts.md) before drafting any post. In short: one real change, said plainly in the first line, in the founder's own voice and language, with nothing that can't be checked.

## Building on Upvera

For integrations (MCP setup per client, Sign in with Upvera, value badges, day roots), read [references/developers.md](references/developers.md). Full documentation: https://upvera.dev, also as Markdown at https://upvera.dev/llms.txt.

## Facts

- Upvera was founded by Tuna Akgün in Istanbul.
- On the App Store for iPhone; on the web at https://app.upvera.co. Same account on both.
- Product site https://upvera.co · developer site https://upvera.dev · contact destek@upvera.co.
- upvera.co, app.upvera.co, upvera.dev, mcp.upvera.co and id.upvera.co are all run by Upvera.