Skip to content

Hubs: the platform, applied to a real kind of work.

A Hub is where the Penvexa Platform stops being an abstraction and becomes a workspace someone can actually use — academic writing, a job search, office work, running a business, software development, or a creative brief, each with its own Hub.

What it is

A domain-specific experience, not a separate product

A Hub is a focused workspace built around one kind of problem — Career Hub around a job search, Academic Hub around coursework and research. Each Hub has its own tools, its own navigation, and its own vocabulary, but none of them are separate products bolted together: every Hub is built on the same underlying platform, the same Engines, and the same engineering standards.

Why it exists

Different work needs a different shape

A single generic AI assistant can technically attempt a resume rewrite and a pull-request review in the same chat window, but it does neither one particularly well — the questions worth asking, the checks worth running, and the output worth trusting are different for each. Hubs exist so each domain gets the interface and workflow it actually needs, instead of everyone sharing one workspace built for none of them specifically.

How it fits the platform

Hubs sit on top of Engines, not beside them.

A Hub doesn't build its own intelligence — it composes existing Engines (reasoning, search, vision, automation) into a workflow shaped for its domain. That's what keeps adding a new Hub from meaning 'rebuild everything from scratch.'

Engines
Reusable intelligence that powers every Hub, built once instead of rebuilt per Hub.
Coming Soon
Forge
Where people will build, customise, and automate their own intelligent workflows.
Labs
Experimental research, prototypes, and the ideas that haven't shipped yet.
Which products use it today

One Hub live, five more built on the same foundation.

  • Career Hub

    The first Hub to ship. Resume Optimizer and Interview Coach are both live products inside it today.

  • Academic, Office, Business, Developer, and Creative Hubs

    Each has a complete product plan and marketing page already written; the underlying Engines are the same ones Career Hub already uses.

How it benefits users

Fewer generic tools, more finished work.

A workspace shaped for the work

A resume workflow and a code review workflow don't share a vocabulary. A Hub gives each domain its own shape instead of forcing one generic interface onto both.

Consistent quality underneath

Because every Hub calls into the same Engines, the reasoning, scoring, and matching behavior a person learns to trust in one Hub carries into the next.

Where it fits

Platform → Hubs → Tools

The Platform is the foundation: Engines, Forge, and Labs. A Hub sits directly on that foundation, applying it to one domain. Inside a Hub, individual Tools — Resume Optimizer inside Career Hub, for instance — are where a specific job actually gets done. Each layer depends on the one below it, never the reverse.

See a Hub in practice

Career Hub is live today, with Resume Optimizer and Interview Coach both shipped.