ready-4 IT

Roles

This page is the central reference for roles, access, approvals, rewards, attribution and workspace logic. The pricing page stays intentionally brief; here is where the actual product logic lives.

Choose a role or the platform logic. Each view collects related information thematically instead of scattering it across prices, workflow, creator and about.

Role

Provider / Developer

Providers and developers build products, define campaigns, control visibility and set the conditions under which testers and creators collaborate. They hold operational authority over programmes, approvals and reward logic.

Control & access

  • Access via the developer portal
  • Products, campaigns and places managed centrally
  • Private or public programmes depending on mode
  • Developer membership as subscription-based access

Selection & quality

  • Relevant testers and creators instead of random volume
  • Testers are assessed before acceptance based on their Vetter activity, GitHub signals and publicly visible work
  • Structured issues and traceable contributions instead of community noise
  • Manual approvals, blocks and re-approvals remain provider-controlled

Rewards & membership

  • Rewards and memberships run consistently through the License Bridge
  • Discounts, licences and slots remain modelled as traceable entitlements
  • VetterPlaces does not sell the developer's product licence

PIM & target platforms

  • For suitable target platforms, VetterPlaces can be used as PIM master
  • Planned targets include Grav and PrestaShop 9.x among others
  • For Grav we provide a Vetter PIM importer so product data flows in a controlled way to the target site

Places & external reach

  • Depending on the product, suitable places are recommended for visibility outside search engines
  • These include product-adjacent communities, specialist forums, creator channels and topically relevant distribution points
  • Places help build reach deliberately rather than waiting only on classic SEO

Workspace logic in detail

RipSnip Only Mode is the private operating mode for programmes that are meant to remain entirely within the GitHub and provider context. The repository stays private on GitHub. Only the owner decides whether, and for whom, a limited ticket exchange via VetterPlaces is enabled.

  • Testers and creators get no repository access and see no general issue backlog
  • Only selected collaborators and approved freelancers may submit structured product tickets
  • Testers only see other tickets when they are relevant and approved within their own Vetter context
  • RipSnip is the bridge between VetterPlaces and private GitHub repositories without exposing the source code
RipSnip Only Mode: approved product tickets without repository access
First model: In RipSnip Only Mode only approved collaborators and freelancers can push tickets into the private provider context. The repository itself stays closed.
Vetter tester with approved context and limited ticket exchange
Second model: A Vetter tester works in the portal and only sees the approved products and the tickets relevant to their own context. RipSnip passes only this approved information to the private repository.
Subscription model Campaign control License Bridge RipSnip PIM

Role

Tester

Testers work with real products in real workflows. Their value comes from reproducible, constructive feedback and a traceable contribution history rather than simple sign-up.

Getting started & applying

  • Free entry via GitHub login
  • Apply to matching campaigns instead of blanket admission
  • Tech stack and activity help with matching

Feedback & quality

  • Clean bug reports instead of vague one-liners
  • Reproducibility and constructiveness count
  • Contribution assessment remains transparently traceable

Rewards & status

  • Fair rewards for verified contributions
  • Discounts or licences come from the respective developer
  • Accepted testers remain active until a genuine block or platform ban applies

Personal interests & co-shaping

  • Testers get free access to products they are genuinely interested in and want to actively use
  • They can help shape the final product and raise specific wishes when nothing comparable exists on the market
  • If the developer provides for it, licence rights may continue after the test period

Visibility & boundaries

  • Clear visibility into what is public and what is private
  • No direct access to private repositories
  • Private provider programmes remain private even with external testers
Free Product fit GitHub vetting Verified rewards

Role

Content Creator

Content creators are a dedicated role for reviews, tutorials, recommendations and visible reach. They do not run as bug testers but follow a separate creator flow with registration, vetting, approval and attribution.

Registration & vetting

  • Free creator registration via your own login
  • Profile, activity, niche and fit are assessed before approvals
  • The assessment is transparently similar to testers but with a creator focus

Benefits & reach

  • Early access to products before the broad launch
  • Coupon codes for your own community
  • Interesting products that make your channel more relevant

Attribution & models

  • UTM-based attribution instead of diffuse affiliate logic
  • Coupon and attribution topics are technically documented in a traceable way
  • Where intended, commission-eligible referrals may be linked to products

Separation & approval

  • No developer membership and no bug-reporting role
  • Own collaboration with providers, separate from the tester flow
  • Creators can also be blocked or re-approved by providers

The creator role on VetterPlaces

No subscription. No hidden costs. A dedicated creator registration.

VetterPlaces offers content creators a free dedicated access for creators who cover software tools and developer products, whether on YouTube, in a blog, podcast or on social media. Entry is via the creator registration with GitHub login; profile, activity and suitability are then assessed and rated similarly to testers before access to campaigns and products is unlocked.

Creator partnership on VetterPlaces

Your role in the ecosystem

  • Provider / Developer builds products and runs programmes
  • Tester delivers reproducible product feedback
  • Creator explains products, builds trust and brings reach

Important: creators are not part of a bug-tracker forum and not automatically provider employees. They work in their own creator flow with a clear task, review and campaign approval.

What creators receive

  • Early access to products before the public launch
  • Exclusive coupon codes for their own community
  • UTM-based attribution: UTM stands for Urchin Tracking Module. These are link parameters that allow visits and registrations to be cleanly assigned to a specific creator campaign
  • Direct contact with the developer teams behind the products
  • Analysis and assessment of their own profile and contributions, transparently similar to testers

No hidden costs

Content creators pay nothing. The model is built on mutual value: you bring reach and authentic reviews, we bring early access, transparent figures and a clear review process. VetterPlaces is not a contracting party for software licences or product purchase agreements. The partnership applies exclusively to platform use and attribution tracking.

How it works

  1. Start registration at vetter.dev.alveos.loc/creator/login.php
  2. Complete your creator profile: add channels, niche, reach and focus
  3. We assess profile, activity and fit similarly to testers
  4. After approval you get access to matching products, coupon codes and UTM links
Free Coupons Transparent attribution

Platform

Platform logic & approvals

Regardless of role, the same core rules apply to visibility, workspaces, attribution, blocks and rewards. This logic belongs in one place and not scattered across prices, workflow and individual pages.

Blocking & re-approving

  • Providers can manually block or re-approve participants
  • This control is deliberately reversible
  • Already accepted participants remain active until a genuine block applies

Rewards, coupons, attribution

  • License Bridge models rewards and entitlements in a technically clean way
  • Coupons and attribution are dedicated creator/marketing topics
  • Product licences and rewards remain the responsibility of the respective developer

Prices & classification

  • Tester: free
  • Content Creator: free
  • Provider / Developer: subscription-based
  • The pricing page shows only the models, not this underlying logic

Public visibility, private repositories and target platforms

  • In RipSnip Only Mode, GitHub repositories remain privately closed. There is no automatic public visibility into issues, comments or code
  • Only the repository owner decides whether a limited ticket exchange with Vetter testers is activated
  • A tester does not see other tickets unless they are relevant and approved within their own Vetter context
  • Public programmes only show the deliberately released opportunity portion, not the internal workspace
  • PIM exports are also part of the platform logic: VetterPlaces can manage complete product descriptions centrally and distribute them in a controlled way to selected target platforms such as Grav or, prospectively, PrestaShop 9.x
Workspace rules License Bridge Visibility