Plans

Three plans, sized to how much organization you have to run.

Every plan is the same application. What changes between them is how much of it is switched on — the scale of the structure you administer, the depth of the reporting, and whether Guidepost exchanges data with the other systems you own. There is no published price list, and no plan is a trial version of another.

Ask which plan fits See what the platform does

The three plans

Each one contains the one before it.

Plans are cumulative. Moving up adds capability and removes nothing, so the page a person learned last week is the page they find next week.

Plan one

Basic

Everything needed to build a course, run it, and prove somebody finished it. A single training unit with courses to author and students to certify has a complete platform here rather than a preview of one.

Course planning and authoring
Enrollment, with pass/fail tracking
Certificates
The per-course completion dashboard
The authoring quality check
A survey's own report, with export and print

Plan two

Middle

Everything in Basic, plus the parts that begin to matter once there is more than one of you — several units under one organization, staff to schedule, and reporting that looks across courses instead of into a single one.

Everything in Basic
The full organizational hierarchy, with multiple schoolhouses and groups
Roster documents
Staff scheduling
Cross-survey reporting, with charts
Scheduled report delivery

Plan three

Highest

Everything in Middle, plus integrations. Guidepost provides a versioned, secure REST API — token-authenticated and working today — so another system in your estate can read from and write to your deployment rather than being kept in step by hand.

Everything in Middle
Integrations
The outbound REST API, which every Guidepost deployment carries
Further integrations in active development

No plan has a published price. Guidepost is sold the same way it is deployed — through a conversation about your organization rather than a checkout. Describe roughly how you are structured and what you need to report on, and we will tell you which plan fits, including when that is a smaller one than you asked about.

Side by side

What each plan switches on.

This table is the whole of the difference between them. Anything not listed here does not vary by plan.

Capabilities included in the Basic, Middle and Highest plans
Capability	Basic	Middle	Highest
Course planning and authoring	Included	Included	Included
Enrollment and pass/fail tracking	Included	Included	Included
Certificates	Included	Included	Included
Per-course completion dashboard	Included	Included	Included
Authoring quality check	Included	Included	Included
A single survey's own report, with export and print	Included	Included	Included
Full organizational hierarchy, with multiple schoolhouses and groups	Not included	Included	Included
Roster documents	Not included	Included	Included
Staff scheduling	Not included	Included	Included
Cross-survey reporting, with charts	Not included	Included	Included
Scheduled report delivery	Not included	Included	Included
Integrations	Not included	Not included	Included

Some things belong to the platform rather than to a plan. The access model and the audit trail, the choice between running Guidepost yourself and having us host it, micro-learning and informational videos, the four-month course schedule, bulk user import, the accessibility work and the three appearance themes, and the REST API described below are all properties of Guidepost itself. They are absent from the table because they do not vary — every deployment has them, on every plan.

The Highest plan

Integrations, led by an interface that already works.

Integration is what the Highest plan is for. One part of it is finished and in use today; the rest is underway, and is described here as underway rather than as a feature waiting behind a plan.

Available today: the REST API

Guidepost provides a versioned, secure REST API. It authenticates with a token your administrators issue and revoke, and it is real, working software rather than a roadmap entry — another system can read your courses, enrollments and completions over it and write back to them, which is usually what people mean when they ask whether Guidepost will talk to something they already own.

It is a capability of the platform and travels with every deployment. It heads this plan because integration work is the reason the Highest plan exists, not because the API is switched off elsewhere.

Not yet available

In active development

Three further integrations are written but unproven. They exist in the codebase and have never been connected to or verified against a real external system, so none of them is something we can switch on for you today. We would rather write that here than let you discover it after a decision.

SCORM export of training completion to an external training-records system
Directory synchronization against a company directory, including Active Directory
Synchronization with an external student information system

Ask where one of them stands. If a particular integration is decisive for you, ask and we will tell you plainly, including when the honest answer is that it is not ready.

Plans and deployment

The plan and the deployment are two separate choices.

They get confused often enough to be worth separating. One of them decides how much of Guidepost is switched on. The other decides who runs the servers. Neither constrains the other.

All three plans exist on both deployment models. A self-managed installation inside your own network can be on any of them, and so can a Guidepost Cloud organization we operate for you. No plan is reserved for hosted customers, and none is withheld from a closed network.

So choosing a plan does not commit you to a way of running it, and choosing a deployment model does not narrow the plans available to you. If you are weighing both at once, say so when you get in touch and we will take them one at a time.

Two independent choices

One from each column

Plan: Basic, Middle or Highest
Deployment: self-managed on your own network, or Guidepost Cloud

The deployment choice in full →

Air-gapped networks are not a lesser case. A closed deployment can be on the Highest plan. What a closed network cannot do is reach us over the internet, which is a hosting question rather than a plan one.

Choosing

Most organizations can place themselves in a sentence.

If you cannot, describe your shape when you get in touch. Recommending more platform than somebody needs is a poor way to start.

Basic, if you are one unit

You have courses to author, students to enroll and certificates to issue, and the whole operation reports to one place. Nothing about that is served better by a larger plan.

Middle, if there is more than one of you

Several schoolhouses or groups under one organization, staff whose time has to be scheduled, or a question that can only be answered by looking across courses rather than into one.

Highest, if Guidepost has to talk to something else

Another system in your estate needs to exchange data with your deployment, and you would rather that happen over an interface than over a spreadsheet somebody maintains by hand.

See the full feature index

Next step

Tell us your shape and we will tell you the plan.

There is no price list to request and no checkout to complete. Describe your organization, what you need to report on, and whether anything else has to exchange data with it.

Get in touch Read the FAQ