This page explains what Authgear Support covers, how fast we respond, and what we do when a request is outside Support. It applies to every Authgear plan and to every deployment, whether we host Authgear for you or you run it yourself.
For uptime commitments, see our Service Level Agreement.
Support plans
| Support plan | Community | Standard | Premium | Premium 24x7 | Mission Critical |
|---|---|---|---|---|---|
| Plans | Developer, Business | Business (add-on), Plus, Enterprise | Plus, Enterprise | Plus, Enterprise | Plus, Enterprise |
| Hours | — | Business hours | Business hours | 24x7 for S1 and S2 | 24x7 for S1 and S2 |
| Channels | Discord, GitHub | Email, support portal | + private Slack channel, video call | + private Slack channel, video call | + phone line for S1, named support engineer |
| Named contacts | — | 2 | 4 | 6 | 10 |
| S1 Critical | — | 1 business day | 4 business hours | 4 hours | 1 hour |
| S2 High | — | 2 business days | 1 business day | 8 hours | 4 hours |
| S3 Normal | — | 3 business days | 2 business days | 2 business days | 1 business day |
| S4 Low | Best effort | 5 business days | 3 business days | 3 business days | 2 business days |
| Also included | Upgrade plan review, yearly health check | Upgrade plan review, yearly health check | All of Premium, root-cause report after every S1, quarterly service review |
Business hours are 9 hours a day, Monday to Friday, excluding public holidays, in the time zone and region stated in your order form. Response time is the time to the first reply from an Authgear engineer, not the time to a fix. We keep working on S1 issues until they are resolved or a workaround is in place.
Severity levels
You choose the severity when you open a case. We may change it if the impact turns out different.
- S1 Critical. Authgear is unavailable or unusable in production. For example, users can't sign in or sign up, or there is a security incident. There's no workaround.
- S2 High. A major feature is degraded in production and the workaround is difficult. For example, one login method or MFA fails for a group of users.
- S3 Normal. A minor production issue that has a workaround, or any issue in a non-production environment.
- S4 Low. How-to questions, documentation questions and feature requests.
S1 and S2 are for production only. Outside business hours, open S1 and S2 cases by phone (Mission Critical), by posting in your private Slack channel (Premium 24x7 and Mission Critical), or with a ticket in the support portal, so that the on-call engineer is paged.
What Support covers
- Authgear doesn't work as described in the documentation: errors, outages and bugs in Authgear.
- Questions about how a documented feature works, or which setting to use. We answer at documentation level: we point you to the right feature, setting or guide.
- The official Authgear SDKs and the documented APIs (Admin API, OIDC/OAuth endpoints, hooks interface), on supported versions.
- Self-managed deployments installed with the official Helm chart or container images, on supported versions. See Self-managed deployments.
- Account, billing and configuration questions about the Authgear portal.
In one sentence
If Authgear is broken, it's Support. If your code or your setup needs our engineers, it's Expert Hours.
What Support doesn't cover, and what we do instead
| Request | Why it's not Support | What we do instead |
|---|---|---|
| "Why doesn't login work in our app?" when Authgear is working as documented | The cause is in the application code, not in Authgear | Expert Hours: we debug the integration together |
| Code, architecture or integration plan reviews | Design and review work | Expert Hours |
| Writing migration scripts, Admin API automation, hooks or custom UI code | Custom development for the application | Expert Hours, or Professional Services for larger work |
| Kubernetes, VMs, databases, networking, ingress, TLS certificates, cloud accounts | Infrastructure outside Authgear | Expert Hours, or a Maintenance plan |
| Installing or upgrading a self-managed cluster | Operations work | Deployment and Maintenance plans; upgrade plan review on Premium and above |
| Unsupported versions, unofficial install methods, modified source code | We can't reproduce them reliably | Upgrade first; Expert Hours to help plan the upgrade |
| Training on OAuth, OIDC, SAML or Kubernetes in general | General education, not product support | Expert Hours (workshops) |
| Calls longer than 30 minutes that aren't about an Authgear fault | Consulting time | Expert Hours |
| New features or custom behaviour | Product work | Feature request (S4), or Professional Services |
We ask before we bill
The first 30 minutes of looking into any case are always free. If a case turns out to be outside Support, the engineer tells you, explains why, and asks before using any Expert Hours.
Expert Hours
Expert Hours are prepaid time with an Authgear engineer for work on your side of the integration: code and integration reviews, debugging your login flows, migration help, architecture and capacity planning, self-managed infrastructure troubleshooting and workshops.
- Sold in blocks of 10 hours. Used in 30-minute steps. Valid for 12 months from purchase.
- Scheduled within 5 business days. Urgent work is scheduled on a best-effort basis.
- Each session ends with a short written summary of the time used and what was done.
Professional Services
Work with a defined deliverable is quoted separately in man-days with a written scope. Examples include custom features, integrations, migration tooling, load testing and custom deployments.
Self-managed deployments
When you run Authgear on your own infrastructure, Support covers the Authgear software. We don't cover the environment it runs in.
| Area | Hosted by Authgear (SaaS, Managed Cloud) | Self-managed with a Maintenance plan |
|---|---|---|
| Authgear software bugs | Support | Support |
| How-to questions about Authgear | Support | Support |
| Infrastructure (cluster, database, network) | Included, we run it | Maintenance plan's included Expert Hours (10 a year), then Expert Hours |
| Version upgrades | Included | Maintenance plan schedule |
| Monitoring and uptime | Included, SLA applies | Maintenance plan |
| Diagnosing an outage | Support | Support for Authgear, Maintenance plan for the cluster |
On a self-managed deployment, response times still apply. But resolving an issue depends on you giving us logs, configuration (with secrets removed) and, where agreed, access. In a disconnected environment we work through a screen share that you run.
Supported versions
- SDKs: the latest major version of each official SDK. We may ask you to upgrade to the latest version before we investigate an SDK issue.
- Community and partner SDKs: not covered by Support. Questions go to the SDK's maintainer.
Your responsibilities
- Open cases from a named contact, with steps to reproduce, the affected project or environment, timestamps, and logs or request IDs.
- Be available to work with us on S1 and S2 cases.
- For self-managed deployments: keep to supported versions and the official install method.
Changes to this page
We will email customers 14 days before any change that reduces what Support covers.