The invited alpha

Greatwait is in an invited alpha. This page explains what that means for you.

​

Who it is for

The alpha is for developers who need an HTTPS callback to reach a service they run, at a time they choose, once or on a recurring schedule, and who can run their own receiver for it.

​

Access is by invitation

You cannot sign up on your own. To join, open the invitation you were sent, set a password, and sign in to the dashboard. Once you are in, you can create projects, destinations, API credentials, and schedules.

If you open the invitation while already signed in with a different account, the dashboard tells you so and offers to sign you out. You can then open the invitation link again.

​

What you bring

An HTTPS receiver of your own. Greatwait delivers callbacks only to an address you control. Your receiver must:

• use HTTPS on port 443,
• be reachable from the public internet (localhost and private network addresses are refused),
• accept a POST and answer with a 2xx status when it has handled the callback.

Greatwait does not offer a shared receiver to try things out, and it will not send your payload to a third-party inspection service for you.

To check each callback’s signature, see Verifying callbacks. Before you begin lists what each quickstart needs as well.

​

Not part of this alpha

Billing and plans are not part of the invited alpha.

​

Your data

You can export a project’s data from the dashboard or with Create a data export. An export covers one environment of one project. An organization administrator can also close the organization from the dashboard, which stops access and delivery at once.

​

Things can change

This is an alpha. Capabilities, bounds, and limits can change while it runs. The published packages are pre-release versions, so pin the exact version you install. The current bounds are listed in Limits.