Public beta guidelines

Keep Heyviber useful, specific, and safe.

Heyviber is for showing real AI-built projects and helping builders improve them with practical feedback. These guidelines keep the beta open without letting noise take over.

Last updated May 31, 2026

Publish projects you can stand behind

Project pages should represent something real enough for others to inspect, try, or review.

Only publish projects you own or are clearly allowed to represent.
Use honest descriptions, working links when available, and relevant stack tags.
Do not publish malware, phishing, credential harvesters, spam, or deceptive clones.

Give feedback builders can act on

Suggestions should help the owner decide what to improve next.

Be concrete about the issue, expected impact, and possible fix.
Use severity and effort honestly instead of exaggerating for attention.
Avoid insults, pile-ons, harassment, or low-effort comments disguised as suggestions.

Use votes and statuses as signal

Votes and owner decisions are there to surface useful ideas, not to win an argument.

Upvote suggestions or projects you genuinely find useful.
Project owners may mark suggestions accepted, implemented, or won't fix.
Project owners may hide inappropriate, abusive, duplicate, or very low-quality suggestions.

Report abuse, not disagreement

Reports go to admin review and should be reserved for content that needs moderation.

Report spam, harassment, scams, security abuse, impersonation, or illegal content.
Do not report a suggestion only because you disagree with its opinion.
Give enough context so the report can be reviewed quickly.

Reports

When in doubt, report it

Janne can review the first beta reports manually. Project owners still control their own suggestion queue, and admin review is the safety net for abuse.

Browse projects Publish a project