Skip to content

Collaboration for engineering teams

Keep engineering conversations, task boards and GitHub connected. Issues become cards, pull requests attach to the issues they close, and check results appear on the board. Use the documented API, bot accounts and scoped tokens to automate further work.

Updated

From a decision to a merged change

A board in table view with filters on status, owner and due date
A team board in table view, with the work synced from the repository.

What is built for it

Context, permissions and an API

  • Context is scattered across four tools

    GitHub sync, both directions

    Issues in, cards out, pull requests attached to the card they close, check results on the card. Writing back to GitHub is opt-in per organisation.

    Read more

  • Every tool brings its own permission model

    One permission model

    A board inherits the roles of the team that owns it, so there is no second access model to administer beside the first.

    Read more

  • The backlog is commercially sensitive

    A documented API

    An OpenAPI document covering the whole surface, with bot accounts, scoped personal access tokens, incoming webhooks and custom slash commands.

    Read more

  • ChatOps needs a real API

    Time against projects, when you need it

    Where hours have to be attributed to a customer or a project, the Time module does it without a second product.

    Read more

For the rest

Build on a documented surface

  • OpenAPIThe whole surface, documented
  • Bot accountsVisible members of the room
  • Scoped tokensPersonal access, per operation
  • Incoming webhooksAlerts and builds into a channel
  • Slash commandsCall your own endpoint
GitHub
Two-way issue and pull-request sync
Boards
Team-owned, inherit team roles
API
Documented OpenAPI, scoped tokens
Automation
Bot accounts, webhooks, custom slash commands
Third-party apps
Not supported — first-party modules only

FAQ

Engineering teams: questions

  • The GitHub module syncs issues into Enclessa board cards, attaches pull requests to the card they close, and surfaces check results on the card. Pushing changes back to GitHub is a setting each organisation enables deliberately. It requires the boards module.

  • Yes. Enclessa exposes a documented OpenAPI surface, with bot accounts and personal access tokens scoped to specific operations, plus incoming webhooks and custom slash commands that call your own endpoint.

  • GitLab, yes: GitLab.com or a self-managed GitLab, and Forgejo or Gitea, mirror their issues and merge requests onto a board, alongside the GitHub connector. There is no Jira connector; Jira is reachable through incoming webhooks, custom slash commands or the API.

Other sectors

The same platform, from another position

Bring your team over this afternoon

Free for up to 10 people, with encrypted direct messages and video calls. No payment card, no time limit, no server to run.

For businesses and organisations only — not available to consumers.

Create your organisationCompare plans