Skip to content

What we do

Everything we offer, in plain words

VibefyCode assesses applications that were built fast — usually with AI — and publishes what it found. Some of what we do is for the person who built something. The rest is for the person about to use it. Each one below says what it is, who it is for, what you end up with, and what it will not do.

Create an accountCheck a badge instead

If you built something

  • Check your own app, free

    Paste your own address and see what a stranger would find in ten seconds: whether it is encrypted, whether it works on a phone, whether anything is in the page source that should not be, whether anybody can reach you.

    Who it is for
    You are about to show somebody what you built, and you would rather find the obvious things yourself.
    What you get
    A list of what to go and fix, each with the evidence and a next step. No account, and nothing kept afterwards.
    What it is not
    It is not an assessment and it earns no badge. It loads one page, once, exactly as a browser would, and there is no score at the end on purpose.

    Check your own app

  • Get your application assessed

    We open your application from outside, the way a stranger would, and work through it against a rubric we publish in full. A person reviews what came back before anything is issued.

    Who it is for
    You built something — quickly, probably with AI — and you need somebody other than you to say what state it is in.
    What you get
    A report you can read and hand to somebody else, a score against each part of the rubric, and, if it clears the mark, a badge for your own site that links back to the evidence.
    What it is not
    It is not a penetration test, a code audit, or any kind of legal certification. It says what was found, on a date, within the scope you authorised.

    See what happens to your app

  • Get your game tested

    The same assessment plus a pass that actually plays the thing: does it become playable, what does it download first, does it work on a phone, does progress survive a reload.

    Who it is for
    You made a browser game. The usual checks ask whether the server answered, which tells you nothing about a loading bar that never finishes.
    What you get
    The same report and the same badge, with a section on how the game behaved when somebody opened it and played for a while.
    What it is not
    We do not say whether your game is any good. Not fun, not original, not pretty. Those are matters of taste and nobody can evidence them.

    What the game pass looks at

  • Keep it watched after the badge

    An application changes. We re-check yours on a schedule, and if what made it pass stops being true, the badge is suspended and you are told why before anybody else notices.

    Who it is for
    Anybody whose badge is on a live site. A mark that was earned eight months ago and never looked at again is worth very little.
    What you get
    Alerts when something material changes, when the application stops answering, and when the rubric it was measured against is superseded.
    What it is not
    It does not watch continuously, and it is not monitoring for an outage. It is a re-check, on a schedule, of the things the badge stands on.

    How re-assessment works

  • Get help fixing what was found

    A fixed-scope engagement to repair the findings. We tell you the conflict before you ask: a company that rates applications and also sells repairs has an obvious reason to find more to repair.

    Who it is for
    You have a report, you know what is wrong, and you would rather not spend three weekends on it.
    What you get
    The work done, and a re-assessment afterwards by a reviewer who had nothing to do with the repair.
    What it is not
    Buying this cannot change a score, move you up the directory, or shorten a queue. Nothing you pay for can.

    The service, and its conflict

  • A page of your own work

    A public page listing the applications you have had assessed, with the marks that are live today, at an address you choose.

    Who it is for
    You build quickly, you would like to be taken seriously, and you have nothing to link to from a proposal or the bottom of a CV.
    What you get
    One page, one address, and a link for each application to the evidence behind it.
    What it is not
    Nothing appears on it until you put it there, one application at a time, and taking any of it down is one action that needs nobody’s agreement but yours. It is a list of assessments, not a rating of you.

    Set one up

  • A trust page we host for you

    Your verification page can carry your own details as well as ours: where somebody writes when something goes wrong, who to tell about a vulnerability, whether the service is up, and your policies.

    Who it is for
    You have a badge, and people keep asking you questions the badge does not answer.
    What you get
    One address to link from your own footer, with the assessment and your own details on it, kept visibly apart.
    What it is not
    We do not check what you write there, and the page says so under your name. It cannot say a badge means more than it does — the same wording rules we hold ourselves to are applied to your text when you save it.

    See what a verification page looks like

  • Be listed where people are looking

    Applications with a live badge appear in a public directory, ordered by what the rubric found and nothing else.

    Who it is for
    Anybody who has earned a badge and would like to be found.
    What you get
    A listing, with your score and the date it was measured, that a stranger can sort and filter.
    What it is not
    The order cannot be bought. There is no promoted slot, no boost, and the ordering rule is published on the page itself.

    See the directory

5 things in every assessment that people do not expect

These are part of an assessment rather than separate products. They are listed because nobody goes looking for them, and they are often the part that turns out to matter.

  • How hard it is to leave

    Every review of every subscription tells you how good it is to join. We measure the other end: how many clicks from the front page to a way out, whether you can do it yourself, and how that compares with how easy it was to start. It has its own rating and its own percentage, and it moves no score.

  • Whether the page holds together

    How many type sizes are on a page, how many of the spacings fall on no scale, whether blocks start a few pixels off each other. None of it is an opinion about taste, and all of it is why a page can feel unfinished to somebody who cannot say why.

  • Whether anybody can use it

    An automated accessibility pass against WCAG 2.2 AA. We run the same one against our own pages on every build, because it is hard to sell an accessibility score from an inaccessible site.

  • A draft accessibility statement, written from what was found

    Every larger company publishes one and every small one knows it should. Most are written from a template, which is why so many claim conformance with a standard nobody checked them against. Yours is assembled from the barriers an assessment actually found, with the sections only you can answer — how somebody reports a problem, what happens if you do not answer, when you will fix things — left visibly empty rather than invented.

  • Where a card number goes

    Whether payment details are typed into a page the merchant controls or handed to a processor. Whether the application asks for more personal data than it explains. Whether anything on the page is a known cryptominer.

If you are about to use something

  • Check a badge you found

    Paste the address of a site carrying our mark, or open the badge itself, and see what the mark actually covers — when it was assessed, against which version of the rubric, and whether it is still live.

    Who it is for
    You are about to trust an application because it carries a mark, and you would like to know what the mark means.
    What you get
    The assessment behind the badge, a plain-language list of what was checked and what was not, and the date it stops being current.
    What it is not
    A live badge does not mean an application has no defects. It means it was assessed, on a date, and met a published threshold.

    Check a badge

  • Check an app before you pay

    A free look at one public page of any application, from outside: can a person be reached, is there a way to cancel, does it say what it does with your data.

    Who it is for
    You are about to hand over a card to something you found yesterday.
    What you get
    An answer in under a minute, with the evidence for each part of it, and nothing kept afterwards.
    What it is not
    It is not an assessment and it earns nobody a badge. It looks at one page, from outside, at a single moment.

    Check an app

  • Read the rubric yourself

    Every criterion, every weight, every threshold, published in full and versioned. A score you cannot check is a number somebody asked you to believe.

    Who it is for
    Anybody deciding whether our opinion is worth anything.
    What you get
    The whole rubric, the version history, and the rule that a badge stays measured against the version it was earned under.
    What it is not
    Reading it will not tell you how any particular application scored. That is on that application’s own verification page.

    Read the rubric

  • A browser extension that checks a site for you

    A button in your toolbar. Click it on any site and it says whether that site carries a live mark, and links to what was checked.

    Who it is for
    You look at a lot of new software and you would rather not open a tab to check each one.
    What you get
    One click, one answer, and no account.
    What it is not
    It does not light up by itself, and that is the point: an icon that lights up on its own has to watch every page you open. It downloads the list of live marks once an hour and answers from the copy on your own computer, so nothing about the page you are on is ever sent to us.

    How badge checking works

  • Reach people who build things

    One advertising space, on a deliberately quiet site, read by people who are shipping software.

    Who it is for
    You sell something builders use, and you would rather not be the fourth banner on a page.
    What you get
    A single placement, clearly marked as paid, with the rate published.
    What it is not
    It cannot buy a score, a listing position, a badge, or a mention in any report. The wall between what we sell and what we assess is the whole product.

    What the space is, and what it is not

What none of this is

Nothing here says an application is safe, and nothing here is a guarantee. An assessment is a point-in-time look at a stated scope, by people who are not lawyers and are not auditors. It does not certify that an application is free of defects, lawful, or fit for any particular purpose.

Nothing you pay us can change a score, a badge, a directory position, or the wording of a report. That is not a policy we could quietly drop: the scoring code structurally cannot read who is paying, and a test fails if it ever can.

How we keep assessment and money apart