Heyviber listed 11 public projects when this article was researched on August 8, 2026. Seven are live products published by Janne Ikola; four are clearly marked demonstration listings. This article uses the live set because each example has a working project page, an external app link, build-tool context and an explicit question for reviewers.

These listings are examples, not endorsements or security certifications. Start with non-sensitive data when trying an unfamiliar app, and read the broader vibe coding project evaluation guide before interpreting a polished interface as production evidence.

The following screenshots are supplied through the public project listings and link back to the owner-controlled context. They show different problem categories rather than seven variations of the same landing page.

The examples fall into four useful patterns.

Make a repeated workflow easier. Peesi packages recurring employee-advocacy activity into challenges and scoring. Kehotesuunnittelija makes prompt construction guided and reusable. Kohdevideo turns a multi-stage media-production task into a defined flow.

Interpret messy evidence. ARVO-AI works with customer-review data; Stockclipper works with consumer and market signals. In both cases, the product must make source context and uncertainty visible because the answer is not valuable if the user cannot inspect why it appeared.

Coordinate AI work under human control. AI-Apuri is not merely a chat screen. Its published scope includes roles, task delegation, budgets, logs and human review. That changes the main product question from “Can a model answer?” to “Can an owner understand and control what several workflows are doing?”

Help a person make a concrete decision. Mitä Ruuaksi?, another live listing in the directory, uses household meal memory to reduce the daily decision burden. The idea is simple; the product work lies in making capture light enough and resurfacing useful enough that the memory improves over time.

The public listings name Codex as the main AI tool for the seven owner-published products. The surrounding stacks differ: Next.js, React, Express, Hono, Prisma, Drizzle, PostgreSQL, BullMQ, Clerk, Stripe, Claude and specialized market or media services appear across the set.

That variety is important. “Built with AI” does not identify the architecture, deployment model, database permissions, payment boundary or operating burden. The AI tool explains part of the development workflow. It does not replace the stack inventory a reviewer needs.

Each owner-published listing names a target user and a problem. It exposes a live app link and a request for feedback tied to the next product decision. Several also disclose maturity: AI-Apuri is described as an active alpha, for example. That context lets a reviewer calibrate expectations.

A toy demo can still teach a technical concept. The distinction matters when a page claims the project is a product. Product evidence includes an end-to-end job, ownership, persistent state where needed, meaningful failure handling, and a way to learn from users. Revenue and scale are not required, but the current stage should not be disguised.

Choose a problem category first. Open the project page before the external app so you know what the owner claims, which tools are disclosed and what feedback is requested. Then complete one low-risk task and write down the exact point where the product became useful, confusing or untrustworthy.

Do not compare projects by feature count alone. A narrow app that solves one repeated task reliably may be more mature than a broad app with many generated screens. Compare the evidence required by the intended use: a creative prototype, internal workflow, public SaaS product and financial research tool carry different consequences.

We inspected the live Heyviber project directory and the individual project pages on August 8, 2026. We included only owner-published listings with external app links in the main gallery and kept the four seeded demonstration projects out of the live-project count. Categories are an editorial grouping based on the published problem, features and feedback request—not builder-supplied labels.

The screenshots come from URLs already published in the project listings. Image sources, appearance, and ownership can change, so readers should check the current listing. We did not claim independent security testing, traffic, revenue, customer adoption, or build-time results.

The Heyviber project directory is the live source. It can change after this article's research date, so use the directory count rather than treating this snapshot as permanent. Builders can publish a project with a clear maturity label, tool list and feedback question so a future gallery can compare genuine evidence instead of promotional claims.