Logo
Opekto.
Try Now

Built by many.
Shaped by you.

Every tool on Opekto exists because someone had a problem worth solving. Suggest the next one, vote on what gets built, and get recognised for the impact you create.

What is the Contributor Program?

Opekto is built on a simple belief - the people who use these tools every day know best what is missing. The Contributor Program is the formal way to turn that knowledge into something real. If you have an idea for a tool, you can submit it, let the community validate it, and if it gets built, you get credited for it permanently. No equity, no vague promises - just transparent, merit-based recognition for genuine impact.

01

Suggest

You spot something missing - a tool that would save time, cut out a repetitive task, or solve a problem nothing else handles well. You write it up and submit it.

02

Earn credit

If your idea gets built and goes live, your name is permanently credited on the tool page. Not a thank-you email. Actual, visible, lasting recognition.

03

Get rewarded

If the tool you suggested consistently performs well over three months, you become eligible for a discretionary goodwill payment based on the traffic and quality it generates.

Free to join. Always.
No follower count. No reputation gate.
Only the idea matters.

How the Contributor Program works

Six steps from raw idea to live tool - with no hidden stages and no ambiguity.

01

Submit your idea

Describe the tool, the problem it solves, and who benefits from it. The more specific and clear you are, the better chance your idea has of moving forward.

02

Verify your email

A one-time link is sent to your email. Your idea only becomes visible to the community after verification - this keeps the queue clean and your identity tied to your submission.

03

The community weighs in

Your idea goes public. Other users can upvote it. The more genuine interest it attracts, the higher it rises in the queue. Ideas with strong community backing move to review first.

04

Review

High-upvoted ideas are reviewed by the team. We look at feasibility, fit, and value. You get a direct email with the outcome - no ghosting, no silence.

05

It gets built

If approved, the tool gets scheduled and built. When it goes live, your name appears on the tool page as the source of the idea. That credit stays permanently.

06

Recognition

Your contributor profile goes live on the Community page. If your tool performs well over the next 3 months, you become eligible for the discretionary goodwill payment.

Revenue share - how it actually works

If your tool performs well, you get recognised for it. This is not a promise of a monthly cheque. It is a transparent, merit-based goodwill framework that rewards genuine impact over inflated traffic numbers.

Read Full Guidelines
≥ 30s avgSession duration

Users must spend meaningful time on the tool, not bounce immediately.

≥ 15%Return visitor rate

Real utility keeps people coming back. Inflated one-off traffic does not qualify.

≥ 60%Organic traffic ratio

Majority of traffic must come from organic sources, not coordinated sharing campaigns.

3 monthsObservation window

Quality metrics must be sustained consistently over three consecutive eligible months.

≤ 60%Unknown traffic cap

If over 60% of traffic in any month comes from unknown sources, that month does not count.

DiscretionaryNature of payment

This is a goodwill gesture, not a contractual obligation. Full terms in the Community Guidelines.

Important:Revenue share eligibility is assessed at Opekto's sole discretion. It is not a contractual right, guaranteed income, or employment arrangement. Eligibility metrics, thresholds, and payment amounts may change at any time. The authoritative terms are always the current version of the Community Guidelines.

Recognised contributors

People who shaped what Opekto is today. Their ideas are live, their names are credited.

View all contributors
A
Arjun MehtaRECOGNISED
Suggested an idea
GitHub
S
Sofia Reyes
Built a tool
GitHub
L
Lena KovačRECOGNISED
Suggested an idea
M
Marcus Obi
Improved a tool
GitHub
P
Priya NairRECOGNISED
Suggested an idea
Community Ideas

Vote on what gets built next

The ideas queue is public and community-driven. Browse open suggestions, upvote the tools you actually need, or submit your own. Your vote directly influences what gets prioritised. The most-wanted tools rise to the top.

More ways to get involved

Ideas are one way in. Reading the rules before you participate is another. Code contributions are a third.

Community Guidelines

The complete rulebook

Every rule, limit, and protection built into the Community Program in one place. Submission requirements, prohibited categories, upvote mechanics, cooling periods, traffic quality standards, revenue share terms, the dispute process, and what gets you permanently removed. Read it before you submit anything.

Read the Guidelines
Code Contributions

Want to contribute code?

If you want to improve an existing tool, fix a bug, build a feature, or propose a technical change, that is handled separately from idea submissions. Share what you have in mind and we will take it from there.

Submit a Code Proposal

Frequently asked questions

If your question is not answered here, the Community Guidelines will have it.

Anyone. There are no geographic restrictions, no follower count requirements, and no technical background gate. If you have a genuine idea for a tool that solves a real problem, you are eligible to submit it.

No. Revenue share under the Contributor Program is a discretionary goodwill payment, not a contractual obligation. Eligibility is assessed monthly based on a quality metrics model - session duration, return visitor rate, and organic traffic ratio - not raw page views. Full criteria are detailed in the Community Guidelines.

One active suggestion per email address at any given time. After a 30-day cooling period following resolution of your current suggestion, you may submit another.

Your suggestion enters a verification step. After email verification, it becomes publicly visible for community upvoting. Once it reaches the upvote threshold, it enters the review queue. You will receive email updates at each stage.

If your idea brings genuinely new functionality or solves a problem the existing tool does not, submit it and describe that distinction clearly. Suggestions that are effectively identical to an existing tool will be closed. If you think an existing tool needs improvement, you can share that feedback through the code contribution instead.

Tools that violate our community standards, generate harmful or illegal content, have no meaningful audience among digital professionals, or depend on closed third-party services with no free access. The full list of prohibited categories is in the Community Guidelines.

Yes. Code contributions - improvements, bug fixes, new features - are handled separately from idea submissions. You can submit a proposal through the code contribution page and we will take it from there.