BluPrint
Product
Documentation
Login
Documentation
Get Started
Use Cases & Guides
Tutorials
Projects
Tasks
Customers & CRM
Business Brain
Views
The Associate (AI)
AI Helpers
Communication
Documents & Knowledge
Time Tracking
Companies & Workspaces
Roles & Permissions
Billing
Account & Profile
Security & Compliance
Integrations
Integrations overview
FAQ
Release LogSoon
ResourcesSoon
DocumentationIntegrationsIntegrations overview

Integrations

BluPrint is preparing a controlled internal production canary. GitHub will be the only approved canary provider, visible only to the canonical Alesko.ai company after activation and verification. Other companies cannot connect a provider. Jira and HubSpot remain unavailable in production.

Open Integrations in the left navigation. Until the canary is activated, no production provider cards are shown.

GitHub canary

Once activated, a company owner or administrator in the Alesko.ai canary can authorise one GitHub connection for the company. The first release is deliberately read-only and manual:

  • choose up to 10 repositories available to the authorised GitHub account;
  • import bounded repository, pull-request, and issue metadata into the company Brain;
  • no source code, diffs, secrets, or file contents are imported;
  • no GitHub writes or actions are available;
  • refresh runs only when an administrator requests it.

GitHub access remains limited by both the provider grant and BluPrint company permissions. The current internal canary may use a broad GitHub OAuth grant as a temporary reviewed exception; customer rollout requires the approved least-privilege GitHub App and a separate data-processing/residency decision.

Consent and tenant controls

  • Connecting requires an explicit, versioned consent acknowledgement.
  • Every connection is reserved and bound to exactly one BluPrint company before it becomes usable.
  • Webhooks are signature-verified and cannot assign an unknown connection to a tenant.
  • Lost callbacks can recover only through the exact unexpired reservation token; unknown connections are revoked rather than adopted.
  • Only owners and administrators can connect, reconnect, refresh, or disconnect.
  • BluPrint stores opaque connection metadata, not provider OAuth tokens.

Pricing and plan limits

The Alesko.ai internal canary is non-billable. Customer rollout remains disabled, but its billing contract is ready:

PlanConnection allowancePrice when customer rollout opens
Free0Not available
BusinessUp to 5USD $2/month per active connection
Business ProUnlimitedUSD $2/month per active connection

A reservation prevents duplicate connections and cap races before provider authorisation finishes. A paid connection becomes active only after its licensed Stripe subscription quantity is confirmed.

Suspension, reconnect, and disconnect

If provider credentials become invalid, sync and connection billing stop immediately while an administrator can reconnect. If the company subscription stops being entitled, sync stops immediately and the connection enters a seven-day recovery period. Recovery within that period restores the same connection; after it expires, BluPrint revokes the provider connection and erases its imported Brain memories.

A manual disconnect follows the same fail-closed cleanup order: block new refreshes, erase imported memories, revoke the provider credential, erase again to close in-flight races, release billing, and retain a temporary revocation tombstone.

Customer connections are not open yet

The production integration surface is prepared to support only the Alesko.ai GitHub canary after activation. Do not expect GitHub, Jira, or HubSpot controls in any company until that activation is complete; broader customer rollout also requires residency approval.

Troubleshooting

If the approved Alesko.ai canary has been activated and GitHub is not syncing:

  1. confirm the connection status in Integrations;
  2. reconnect if BluPrint reports invalid credentials;
  3. confirm the GitHub grant still includes the intended repositories;
  4. wait 10 minutes before repeating the same repository refresh;
  5. contact support if authorisation, cleanup, or billing remains pending.

Next

  • Billing
  • Business Brain
  • Data protection

Last updated: 2026-08-21

On this page

  • GitHub canary
  • Consent and tenant controls
  • Pricing and plan limits
  • Suspension, reconnect, and disconnect
  • Troubleshooting
  • Next