Epiphani Cash pays you for making our software better. Report a bug we confirm, or suggest a feature we go on to build, and $10 in credit lands in your Epiphani account. Bring a fully specced feature idea, or one detailed walkthrough that surfaces several issues at once, and it can earn up to $50. Good toward any Epiphani purchase on our websites.
We practice kaizen: constant, small improvement, every version a little better than the last. The people best placed to spot the next improvement are the people using the software every day. When something breaks on you, or you catch yourself wishing an app could do one more thing, that moment is valuable to us, and we pay for it.
Most software companies route that moment into a feedback form that answers with silence. You rarely learn whether anyone read it, the bug quietly persists for two more releases, and the lesson you take away is that reporting things is a waste of your time. We think that arrangement wastes the product truth we value most: a real person, in a real moment, telling you exactly where the software fell short of what they needed.
So we flipped it. You report it, a person reads it, we fix or build it, and your name goes on the public ledger next to the improvement you caused. The credit is real spending power against anything in the catalog on our websites, and the ledger is the studio’s improvement history, written together with the people who use it. Every entry on it is a moment the software got better because someone bothered to say something.
This program covers every app the studio ships: document readers, performance tools, contact managers, travel planners, photo tools, and the websites that sell them. If you can see it and it carries an Epiphani name, a confirmed find in it pays.
The economics are squarely in our favor, which is why we expect to keep running this. A bug that survives in a shipped app costs us more than $10: it costs a refund here, a bad first impression there, and hours of a developer’s time reconstructing from a vague complaint what you could have told us plainly in two minutes. Paying you to describe it precisely, at the moment you hit it, is cheaper than reconstructing the same fact from a refund request. We are not being charitable: a $10 report that arrives while the details are fresh saves far more than $10 of reconstruction later, and the people using the apps every day are the ones closest to those details.
Why credit rather than cash. In our judgment, cash bounties at this size invite people who farm forms for money without touching the software. Store credit pays the people the program is actually for: the ones already inside the apps, hitting real edges, who will spend the credit on more of what they already use. It keeps the loop closed, the reports genuine, and the reward meaningful to exactly the person who earned it.
Three steps, and a person at every one of them. No triage bots, no auto-closed tickets.
Two minutes, right here. What happened, or what you wish existed. The email you give is where your credit lands.
A person reads every report. If we can reproduce the bug, or we decide to build the idea, it counts. You hear back either way.
Epiphani Cash appears in your account, good toward any catalog purchase on our websites. The fix enters the queue, and the ledger records your find.
What happens after you press send. Your report goes straight into our own review queue, and a person reads it, usually within a few days. Bugs get an attempt at reproduction: we open the app you named, follow the steps you described, and watch for the failure you saw. Ideas get a product decision: is this something we want the app to do, and are we willing to commit to building it?
The statuses you will see on the ledger. A bug we reproduce is marked confirmed, and marked fixed when the repaired version ships. An idea we commit to is marked accepted the day we say yes, and shipped the day it is real. Credit is granted at confirmed or accepted, so you are paid for the find itself, and you get the second note when the work lands.
First reporter earns it. If two people report the same bug, the credit goes to whoever told us first, and we say so honestly to the second. Duplicates still help us judge severity, but the bounty is a finder’s fee, and the finder is whoever found it first.
The quick finds pay $10. The big ones are graded up to $50.
For a confirmed, reproducible bug in any Epiphani app or website: a broken button, a spelling mistake, a confusing moment, text you cannot read. First reporter earns it. Tell us what you did, what you expected, and what happened instead.
Suggest a feature. If we agree and commit to building it, the first person who suggested it gets the credit the day we say yes, and a second note the day it ships.
Two shapes earn the top of the ladder. A feature idea specced so well we could build from it: the problem moment, who it serves, how it should work, the edge cases you already thought through. Or one organized walkthrough that surfaces several distinct issues in a single pass. The reviewing team grades each on the quality of the thinking, the detail of the work, and how much it improves the software; $10 is the floor whenever any single piece of it is confirmed.
You do not need to be technical. You need to be specific. Here is what makes a report land on the first read.
An example that would pay. “In the reader, I opened a 200-page PDF, searched for a word I could see on screen, and got no results. I expected the search to find it. Happens every time on this file, on my Mac.” That is reproducible, specific, and honest about scope. If we can make it happen too, it is confirmed, and it pays.
An example that would probably not. “The app feels slow sometimes.” We believe you, but there is nothing there a person can reproduce: no app named, no action, no moment. Vague reports do not count against you; they simply cannot be confirmed, and we will write back asking for the missing piece rather than closing the door.
What earns the full $50. Detail and effort. A specced feature reads like a plan we could hand to a developer: the moment that made you want it, who else would use it, how each screen should behave, and what should happen at the edges. A walkthrough reads like a guided tour: you moved through an app or a website with intent, and every stop on the tour is a distinct issue we can confirm on its own. Either one is graded, and the grade rises with the quality of the suggestion and the work you put into it.
Cosmetic counts. A misaligned button, a label that lies, text you cannot read in dark mode: if it is real and we can see it, it is a bug like any other. Many strong finds are the small ones a developer stops noticing after the hundredth build.
What happens to a find we cannot confirm. It does not vanish. Reports we cannot reproduce stay in the queue with your email attached, and when a later report, a crash log, or our own testing finally makes the failure visible, the confirmation and the credit go back to the first person who described it. Some bugs take weeks to earn their $10; the queue has a long memory, and being early still counts.
You are not hunting. You are just using the apps, with the reporting reflex switched on.
You are reading a document and the search comes back empty on a word you can see. You are cleaning up your contacts and a merge does something you did not ask for. You rename a file and the old name is still showing an hour later. A window comes back in the wrong place. A keyboard shortcut that worked last month does nothing now. Dark mode makes one label unreadable. An export produces a file that will not open.
Each of those is two minutes of your time and $10 of ours, and when we confirm one, the fix reaches everyone who never noticed. The same reflex works in the other direction: every time you catch yourself saying “I wish it just did this,” that sentence, written down with the moment attached, is a candidate for the idea bounty.
When a find occurs to you away from your desk, email works as well as the form: hello@epiphani.studio, any format, any length. A person reads that inbox too.
Every confirmed find and accepted idea is recorded here with the contributor’s chosen display name, or unlisted where they prefer: the running record of who made what better.
| Contributor | App | Find | Status | Awarded |
|---|
Software companies do pay for reports, but the paid programs that exist are aimed at professional security research, as the table shows. Here is the map.
| Program | Pays for | Award | Paid as | Open to |
|---|---|---|---|---|
| Epiphani Cash | Ordinary bugs and feature ideas in consumer apps and websites | $10 per confirmed find, up to $50 for specced ideas and walkthroughs | Store credit toward any Epiphani purchase on our websites | Anyone who uses the apps |
| Apple Security Bounty | Security vulnerabilities only | Up to $2,000,000 base, past $5,000,000 with bonuses | Cash | Security researchers |
| Google’s Vulnerability Reward Program | Security vulnerabilities in Google products | Scaled by severity, per its published reward tables | Cash | Security researchers |
| A typical consumer app’s feedback form | Bugs and ideas | Nothing | A thank-you, sometimes | Anyone |
Where the big programs win, plainly. If you do professional security research, Apple and Google pay incomparably more than we do, in cash, and their programs are the right place for that work. We are not competing with them and it would be silly to pretend otherwise. A security vulnerability in one of our own apps also skips this program: email it to hello@epiphani.studio directly, it is never published, and it earns a larger thank-you than the standard bounty.
Where this program is different. The security programs pay nothing for the finds ordinary people actually make: the broken export, the wrong label, the feature that should exist. That is the gap Epiphani Cash covers. It pays for the everyday find, requires no security skills, and answers every report with a person rather than an automated triage queue.
Epiphani Cash is store credit against any Epiphani product bought on our websites. It sits in your account at account.epiphanistudios.com, tied to the email you reported with, and it stacks: three confirmed finds is at least $30 toward whatever you want from the catalog, and a single well-built walkthrough can be $50 on its own.
When you are ready to use it, reply to your grant email, or write to hello@epiphani.studio, and we apply it to your order within a day. A checkout that applies it automatically is planned; today a person does it, quickly.
The fine print, plainly: it is promotional credit, so it has no cash value and is non-transferable, and it cannot be applied to App Store purchases, which Apple processes end to end. Credit expires 12 months after it is granted, which is plenty of time to spend it and short enough that the books stay clean.
The ceiling is real but generous: at the $100 monthly cap, a steady reporter can earn up to $1,200 of catalog credit in a year. Nobody has done that yet. Somebody eventually will, and we will be delighted to pay it, because a year of that person’s finds is worth far more to the software than the credit costs us.
Bug or idea, same form. A person reads it and you hear back at the email you give.
Epiphani Cash is a discretionary thank-you program run by Epiphani Studios. We may adjust or end the program at any time; credit already granted stays granted per these terms. Questions: hello@epiphani.studio.
What we collect when you report. Exactly what the form shows: the type of find, the app, your one-line summary, the details you write, and your email. It goes into our own database, on our own infrastructure, and it is read by a person. We use your email for two things only: replying to your report, and granting your credit.
What gets published. Only confirmed finds and accepted ideas appear on the ledger, and only with the display name you choose; choosing to stay unlisted takes one click at claim time. Your email is never published, and the details of your report are summarized, never posted verbatim, so nothing you wrote in frustration at one in the morning follows you around.
What we never do. We do not sell your data, share it with advertisers, or use your report for anything beyond running this program: confirming, fixing, building, and paying. Security reports are held out of every public record entirely.
Analytics on this site. Off unless you say yes. The site ships with analytics disabled by default; it only measures anything if you opt in, and even then inputs and text are masked. No consent, no measurement, and the report form works identically either way.
No. The only personal detail the form asks for is an email, so we can reply and pay you. An Epiphani account gets created around that email when your first credit is granted, and you can claim it at account.epiphanistudios.com whenever you like.
A person reads every report, usually within a few days. You hear back whether the answer is yes or no; silence is not one of the outcomes.
It is real spending power with a boundary: $10 to $50 of store credit per find, good against any Epiphani product bought on our websites, and stackable across finds. It is not cash, it cannot be transferred, and it cannot be applied to App Store purchases, which Apple processes.
Detail and effort, in one of two shapes: a feature idea specced well enough to build from (the problem moment, who it serves, how it should work, the edge cases), or one organized walkthrough that surfaces several distinct confirmable issues in a single pass. The reviewing team grades each on the quality of the thinking, the detail of the work, and how much it improves the software. $10 stays the floor whenever any single piece is confirmed.
One we can reproduce. We follow your steps in the app you named, and if we see the failure you saw, it is confirmed and it pays. If we cannot reproduce it, we write back and ask for the missing detail rather than closing it.
The first reporter earns the credit, and we tell you honestly that you were second. Your report still helps: duplicate reports tell us how many people a bug actually reaches.
Acceptance means we commit to building it, and that decision is entirely ours. Most ideas will not be built; the ones that land usually come with a real moment attached: when you wanted it, what you did instead. You are paid the day we say yes, with a second note the day it ships.
Yes: $100 per person per month, applied in the order your finds are confirmed. Whatever lands past the cap queues for the new month the same way. Finds beyond the cap still count, still get fixed, and still enter the ledger with your name.
Twelve months after it is granted. Spend it on anything in the catalog before then; the grant email tells you the date.
Skip the public form and email hello@epiphani.studio directly. Security reports are never published, are handled first, and earn a larger thank-you than the standard bounty.
No, and we never will. Reviews bought with credit are worthless to readers and poison for trust. This program pays for improvements, never for praise.
Every app Epiphani Studios ships, on every platform we ship it on, plus our websites. The form lists the current catalog; if you found something in a product we make that is not listed, pick “Something else” and name it in the details.
Yes: hello@epiphani.studio, any format. The form exists because it prompts you for the details that make a find confirmable, but the inbox is read by the same people.
You already notice what is wrong with software. Most companies ask you to swallow that noticing, or to donate it to a form that never writes back. We would rather buy it from you: $10 for every confirmed bug, $10 for every idea we build, up to $50 for a fully specced idea or a detailed walkthrough, your name on the ledger, and the fix on its way to everyone.
The next time an Epiphani app does something it should not, or fails to do something it should, that is not an annoyance. That is a find.