Skip to main content
Help & Support

Get help with Ever Teams

Ever Teams is developed by Ever Co. LTD and runs both as a self-hosted, open-source platform and as a cloud service at app.ever.team. Here is where to get help, which channel fits which problem, and how to make your request easy to answer.

Choose the right channel​

Picking the channel that matches your problem is the fastest route to a useful answer.

Solve it yourselfCommon errors, fixes, and frequently asked questions.Ask the communityQuick questions and general chat on Discord.Report a bugReproducible defects, on GitHub Issues.Request a featurePropose an idea in the feature requests repo.Report a vulnerabilityPrivately, to [email protected] — never a public issue.Commercial supportLicensing, billing, custom development, enterprise.

Full channel details, including Slack and Gitter, live on the Contact Us page.

Before you ask​

Most reports resolve faster when they arrive complete. Work through this list first.

  1. Search the docs — start with Troubleshooting & FAQ, then Getting started and Configuration.

  2. Search existing issues — your problem may already be reported, or already fixed on develop.

  3. Check the API is reachable — visit https://api.ever.team/api/health, or your own API host, and confirm it responds.

  4. Reproduce on a clean state — clear browser cookies and local storage, or rebuild without the .next cache.

  5. Check the console and server logs — the actual error message is usually already there.

What to include in a report​

A good report answers what did you do, what did you expect, what happened instead — and gives us enough to reproduce it.

VersionRelease tag or commit SHA.
DeploymentCloud, self-hosted, or local development.
ApplicationWeb, desktop, mobile, or browser extension.
EnvironmentOS, browser, Node.js version, Docker and Compose versions.
BackendEver Gauzy API URL and database — PostgreSQL or SQLite.
Steps to reproduceNumbered, starting from a fresh session.
Expected vs. actualWhat should have happened, and what did.
EvidenceConsole output, server logs, screenshots, or a short recording.
Redact your secrets

Logs and .env files contain API keys, database credentials, and tokens. Strip them before pasting anything into a public issue or a chat channel.

Self-service resources​

DocumentationSetup, architecture, features, deployment, API.GuidesPractical guides to work & time tracking.Live demoTry the platform with no installation.Product demoGuided walkthrough, including the Kit.DownloadsDesktop, mobile, API server, Docker images, source.RoadmapWhat is planned and what is in progress.BlogRelease notes, news, and updates.Free toolsPomodoro timer, time card, timer, time converter.Open sourceHow the project is built and governed in the open.PartnersPartner program and implementation help.

Community support​

Community support is free and covers the open-source Community Edition. It is best-effort — maintainers and other users answer as they are available, and there is no response-time commitment. Every channel, and what each one is best for, is listed on Contact Us.

Ask once, in one place

Post your question in a single channel and link to it if you need to follow up elsewhere. Cross-posting the same question splits the answers.

Support by plan​

Cloud plans are tiered by number of active users, and one purchase covers both the Platform and the Kit. See ever.team/pricing for the current tiers, limits, and prices.

For cloud accounts, Ever Teams lists email and live chat as the support contact methods — see the FAQ on the pricing page for the current commitment. Subscription details, credits, and license upgrades are managed from your account dashboard, and an upgrade credits the cost of your current license toward the new one.

Commercial & enterprise support​

Beyond the community channels, Ever Co. offers paid engagements:

  • Priority and dedicated support for production deployments
  • Custom development and feature sponsorship
  • Deployment and migration assistance for self-hosted installations
  • Commercial licensing — Enterprise and Small Business licenses for use outside AGPL-3.0 terms

See Contact Us for how to reach the team, and ever.team/partners for implementation partners.

Self-hosted support​

Self-hosting means you own the deployment, so most issues are environment-specific. Ever Teams requires a reachable Ever Gauzy API — either the hosted one at api.ever.team or your own instance.

Before opening an issue, confirm:

  • The API URL is set in both GAUZY_API_SERVER_URL and NEXT_PUBLIC_GAUZY_API_SERVER_URL
  • The API responds at /api/health
  • CORS allows your web app's domain
  • Ports 3030, 3000, 5432 and 6379 are free, and Docker has at least 4 GB of RAM allocated

See Deployment and Troubleshooting for the details, and Configuration for the full environment variable reference.

Service status​

The ever.team footer publishes a live system status indicator for the hosted services. If the cloud app or API is unreachable, check there before filing a report. For self-hosted deployments, check your own API health endpoint and container logs first.

Security issues​

Vulnerabilities go through private disclosure, never a public issue. Include affected versions, reproduction steps, and impact — the Security guide covers the full process, and Contact Us has the address.

Helping others​

Support goes both ways. Answering someone else's question, or fixing the page that would have answered it, is the fastest way to improve it — every page here has an Edit this page link at the foot.

See Community for the other ways to contribute.

Resource and status details on this page are sourced from ever.team and ever.team/pricing.