Everything about Jellar
Your complete guide to building, testing, and earning on Jellar.
What is Jellar?
Jellar is a Human Signal testing platform for AI builders — people who use AI to build apps, tools, and products fast (sometimes called "vibe coders").
The problem: you can build something in a weekend with AI, but getting real humans to actually test it is hard. Friends are too polite. Social media is too noisy. User research firms are too expensive.
Jellar solves this. Builders list their projects, Testers review them with structured feedback, and everyone earns karma and credits for participating.
How it works
A builder lists their project with a URL, a short mission for testers ("try to sign up and send a message"), and answers a safety questionnaire. Automated checks run instantly, then a human admin reviews within 24 hours.
Approved projects appear on the Pulse globe and the Ladder. They're ranked by tier, then by builder karma within each tier. Sponsored projects sit at the top in gold.
Testers pick a project, read the briefing, then click to open it in a new tab. A 3-minute timer enforces minimum dwell time. Testers fill in structured feedback — friction points, magic moments, a summary.
Testers earn Vibe Credits and karma based on completeness. Builders see reviews in their dashboard. Builder karma improves, lifting their project higher on the Ladder.
Builders vs Testers
Builders
You've made something and want real feedback. You submit your project, define a mission for testers, and earn builder karma as reviews come in. Higher builder karma = higher position on the Ladder = more visibility = more reviews.
Testers
You spend 5–60 minutes using someone's build and give structured, honest feedback. You earn Vibe Credits and tester karma for every completed review. High tester karma gets you on the leaderboard.
Most people are both. Builders are encouraged (and on some tiers, required) to test other projects before listing their own. This keeps the community healthy.
Submitting a project
- Sign in with GitHub. Your account must be at least 5 days old.
- Go to Submit and fill in the form. You'll need a live HTTPS URL, a category, a mission brief, and answers to the Vibe Check safety questions.
- Automated pre-flight checks run instantly in your browser. If any fail, you'll see exactly why and how to fix it.
- If all checks pass, your submission enters the manual review queue. A human reviews it within 24 hours.
- Approved → your project goes live on the Pulse globe and Ladder. Rejected → you'll see the reason and can resubmit after fixing the issue.
Missions are currently capped at 60 minutes. If your project needs a longer test (e.g. tracking something over days), that requires a paid bounty mission — coming soon. For now, design your mission to fit within an hour.
Project categories
Pick the category that best describes what your project does, not what technology it uses. Not sure? If AI is the whole point of the product, pick AI Tool. If AI is just under the hood, pick the category that describes the user-facing purpose.
AI or an LLM is the core feature — chat assistants, AI writers, code generators, image tools, AI search.
Built for developers. APIs, CLIs, code helpers, debugging tools, deployment dashboards, devex improvements.
Helps people get things done. Task management, note-taking, workflow automation, scheduling, focus tools.
B2B or business-focused software. CRMs, dashboards, reporting tools, team collaboration, ops software.
Tools for making things look or sound good. Image generation, video editing, typography, brand tools, music.
Money-related tools. Budgeting, invoicing, expense tracking, payments, crypto, personal finance.
Fitness, mental health, habit tracking, nutrition, sleep, meditation, and wellbeing tools.
Tools that teach or help people learn. Courses, tutoring, flashcards, skill trackers, language learning.
Selling things online. Shops, marketplaces, product discovery, inventory tools, dropshipping.
Games of any kind, interactive experiences, browser toys, party games, entertainment apps.
Tools for talking to people. Chat apps, email clients, team tools, newsletters, social features.
Tools for understanding data. Dashboards, reporting, data viz, analytics, business intelligence.
Tiers explained
Your tier determines how many reviews your project can receive, how many domains you can list, and whether you need to complete missions before posting. Within each tier, projects are ranked by builder karma.
Reviews per mission
Each tier caps how many testers can review your project in a single listing period. Once the cap is reached, no new testers can be assigned — you'd need to resubmit (Tier 3) or start a fresh submission. Tier 1: 10. Tier 2: 25. Tier 3: 50.
Active domains
How many distinct domains (project URLs) you can have listed at one time. Tier 1: 1 domain. Tier 2: 2 domains. Tier 3: unlimited — meaning any number of separate projects across any number of domains, all active simultaneously.
Listing duration
How long your project stays live on the Pulse before it automatically expires. Tier 1: 7 days. Tier 2: 14 days. Tier 3: 30 days. Expired listings are archived — testers can no longer be assigned. With vibe coding, a lot can change in a week — expiry keeps the Pulse fresh and ensures testers are seeing current builds, not abandoned ones.
Resubmit button (Tier 3 only)
Tier 3 builders get a one-click Resubmit button on their profile. This refreshes the listing with the same details — resetting the review count to zero and the listing timer — without having to fill in the form again. Tier 1 and Tier 2 builders must fill in a fresh submission each time.
Must review missions before submitting own build
To keep Jellar reciprocal, some tiers require you to complete a set number of missions as a tester before you can list your own project. Tier 1: 5 missions. Tier 2: 1 mission. Tier 3: none required. This ensures builders understand what it feels like to be a tester — which makes their own mission briefs better.
Ladder position
The Pulse Ladder is divided into sections by tier. Sponsored projects sit at the top in gold. Tier 3 projects occupy the next section. Tier 2 below that. Tier 1 at the base. Within each section, projects are sorted by builder karma — the more karma you have, the higher you appear within your section. Higher position = more visibility = more testers finding your project.
Comprehensive AI testing (Tier 3)
Tier 3 builders receive an AI-assisted analysis pass across all their feedback sessions. This surfaces patterns across multiple reviews — common friction points, contradictions between testers, what most people struggled with, what most people loved — and produces a prioritised list of recommended fixes. This is above and beyond what any individual tester can provide. Coming soon.
Sponsored slot
A sponsored slot places your project at the very top of the Ladder in gold for 7 days, above all tier sections. Your globe marker also appears in gold, standing out from all other projects. We limit the number of active sponsored slots to maintain quality. Sponsored slots are available to any builder regardless of subscription tier and are priced by enquiry.
Priority support (Tier 2 and 3)
Tier 2 and Tier 3 builders get priority responses to submission reviews, appeal requests, and platform questions. During the MVP period this means a human response within 24 hours. Tier 1 and free accounts are handled in order of request.
Payments are coming soon via Stripe. During the MVP period, all accounts have testing access with admin-granted tier exceptions.
Pre-flight checks
These run automatically in your browser when you hit submit. Here's exactly what each one checks.
01 — HTTPS required
Your URL must start with https://. Unencrypted http:// sites are a risk to testers.
02 — Valid domain format
Must be a real domain (e.g. myapp.com), not a raw IP like 192.168.1.1.
03 — Not a URL shortener
Blocks bit.ly, tinyurl.com, t.co, goo.gl and similar. Shorteners hide the real destination.
04 — No banned TLDs
Rejects .tk .ml .ga .cf .gq .zip .mov — disproportionately used for abuse.
05 — No phishing patterns
Scans for brand impersonation: paypal-secure, apple-login, google-verify, etc.
06 — No lookalike characters
Rejects punycode (xn--) or non-ASCII characters used to impersonate real domains (e.g. Cyrillic letters that look like English).
08 — Account at least 5 days old
Your Jellar account must be ≥ 5 days old. Prevents throwaway account abuse.
09 — URL not already submitted
Blocks duplicate submissions. If your URL is listed and you're the real owner, contact us.
10 — Description matches content
A basic keyword match between your description and the site's visible text. Catches obvious mismatches.
11 — Site appears online
Confirms your site is actually reachable. A fail means it's down, not deployed, or blocking requests.
Manual review
After automated checks pass, a human admin opens your site and checks:
- Does the site match what you described in the Vibe Check?
- Is the mission actually doable in the stated time?
- Are there hidden dark patterns, misleading flows, or tester risks?
- If test credentials were provided, do they work?
- If AI is claimed, is it actually present?
Most submissions are reviewed within 24 hours. You'll see status updates on your profile page.
Doing a mission
- Pick a project from the Pulse Ladder on the homepage.
- Read the Mission Briefing — it tells you what the builder wants you to do, what the project is about, and any warnings (login required, data collection, etc.).
- Click Open Project + Start Timer. This opens the project in a new tab and starts a 3-minute minimum dwell timer.
- Use the project as a real user would. Actually try to complete the mission.
- Come back to Jellar and fill in the feedback form. The more you fill in, the more credits you earn.
- Submit. Credits and karma are awarded immediately.
You can only review each project once. If the builder submits a new version (new URL or updated Vibe Check), you can review again.
Karma & Credits
There are two separate karma scores:
Tester Karma
Earned by completing reviews. Higher tester karma puts you on the Top Testers leaderboard. Leaderboard position boosts visibility — especially if you have a live project, since clicking your name highlights your build.
🔥 Sponsored missions pay DOUBLE karma — complete a sponsored mission to earn 2× credits. Look for the gold badge on the Ladder.
Builder Karma
Earned when testers complete your missions. Higher builder karma moves your project up the Ladder within your tier. More visibility = more reviews = more karma = more visibility.
Rewarding great reviews
When you receive reviews on your project, you'll see a +1 karma button next to each one on your profile page. If a tester gave you genuinely useful, specific feedback — use it. It's a small signal that says "this person did the work."
Go to your Profile page → Reviews Received. Each review card has a "+1 karma" button. Click it to award one karma point to that tester. You can only award it once per review.
Karma affects a tester's position in the leaderboard and their reputation on the platform. Testers with higher karma are more visible to other builders. Quality feedback gets rewarded.
To keep the leaderboard and Ladder reflecting active community members, karma decays for inactive accounts.
- If you haven't submitted any reviews in 30 days, your tester karma drops by 15% on the 1st of the following month.
- Decay is floored at 0 — you won't go negative.
- Builder karma decays by the same rule if your project receives no reviews in 30 days.
- You'll receive an email warning before decay kicks in. (Email notifications coming soon.)
The fix is simple: complete one review, and the 30-day clock resets.
Feedback quality
Good feedback is specific. "The UX is bad" is useless to a builder. "The sign-up button wasn't visible on mobile — I had to scroll down to find it" is gold.
Good feedback
- Specific friction points with context
- What you expected vs what happened
- Your honest "would I use this again" answer
- The single most important thing to fix
What gets flagged
- Vague one-liners with no detail
- Copy-pasted responses across sessions
- Profanity or abusive language
- Submitting feedback without actually using the product
What gets you banned
- Submitting a project you don't own without permission
- Lying on the Vibe Check questionnaire (hiding data collection, payments, or login requirements)
- Submitting phishing, malware, scam, or illegal content
- Using Jellar to harvest test credentials or personal info from testers
- Creating throwaway accounts to bypass submission limits or review gates
- Submitting fake or bot-generated feedback
Bans are tied to your GitHub account and IP. Ban appeals can be sent to the email on your GitHub profile.
Language policy
All project submissions, mission briefs, and feedback must currently be written in English. This is a platform requirement during early access to ensure our team can review all content. Support for additional languages is on the roadmap — see the Roadmap for details.
Jellar is a professional feedback platform. The system automatically blocks profanity and prohibited language from all submissions and feedback. If your text contains profanity, the field will be highlighted and you'll be asked to remove it before you can proceed. It simply won't go through.
This applies to project titles, mission briefs, descriptions, and all tester feedback fields.
FAQ
Still have questions? Reach out via GitHub or email.
READY TO SUBMIT →About the name
The name JELLAR traces back to Gjallar — a word from Old Norse meaning to resound, to yell, to broadcast a signal. In Norse mythology, the Gjallarhorn is the horn of Heimdall, the watchman of the gods. When sounded, it sends a signal across all nine worlds — a call to attention that cannot be ignored.
That's the idea behind this platform. Builders ship things into the void. Jellar is the horn — it broadcasts their signal to the humans who will actually listen, test it, and send back a real response.
The original team behind Jellar has Scandinavian heritage, and Norse mythology felt like the right well to draw from — timeless, a little dramatic, and genuinely about communication across distance. It also has a stellar ring to it, which felt right for something meant to travel far.
The domain was available. The gods aligned. Here we are.