Skip to content
Dokeo
Scan a draft

Roadmap

The gate starts with content, and it keeps going from there.

What ships today, what is built but not yet sold, and where it goes next. We only market what is live.

Live today

  • Content quality gate

    19 checks across SEO, AEO and GEO for 17 content types, one verdict per draft.

  • Every surface

    Web app, REST API, CLI, MCP server and webhooks, plus the public GitHub Action.

  • Review queue

    A person signs off before a draft ships.

  • Citation watch

    After publish: is the page getting cited by AI assistants.

In Labs

  • Exposure register

    One list of everything a scan flagged, with severity and a due date. Built; being hardened.

  • Intent signals

    Buyer-intent signals next to the content they relate to. Built for one provider.

  • Security checks

    Confidential data and personal data in drafts. These two already run on every scan.

  • Agents

    Drafts for follow-up work, always approved by a person. Dokeo never sends anything itself.

Next

  • Organizations and roles

    Teams, roles and invitations on one account, with single sign-on after that.

  • One database

    Accounts, keys and billing on Postgres with backups, replacing file storage.

  • More surfaces

    The same ship-or-fix idea for CRM data, outbound copy and pipeline hygiene.

The idea

Every revenue team ships work nobody checks.

Content was the first place this broke: more drafts than editors, and AI search changing what good looks like. The same gap exists in CRM data, outbound and pipeline. The plan is one gate pattern for all of them, one surface at a time, each one live before it is marketed.

Try the content gate Read the changelog