ENTERPRISE

Codebase intelligence, negotiated to your environment.

Enterprise is a conversation, not a template. Pricing and scope are negotiated per organization — tell us what your environment actually requires.

Included today

✓Everything in Team
✓Bring your own AI key — encrypted, used only for your account's analyses
✓Dedicated support

Worth raising in conversation

—On-premise or self-hosted deployment
—SSO for your identity provider
—Compliance requirements specific to your industry

None of these ship as a self-serve feature today. They are the kind of thing an Enterprise deal can scope in — ask, rather than assume either way.

Integrations

✓

GitHub Issues

The default source. Selectable with no setup beyond the GitHub connection your repository already uses.

✓

Jira

OAuth connection from the Tickets tab. Once connected, Jira is a switchable source alongside GitHub.

✓

Azure DevOps

Connect with a personal access token, then pick a project.

✓

Slack

A webhook URL in Settings → Autopilot posts the daily brief there, in addition to email.

Linear support is on the roadmap, not shipped yet.

Looking for something specific to your role?

CTO / VP Eng →Engineering manager →Software architect →Agency / consultant →Evaluating an acquisition →

Not sure? Everything on this page applies regardless of role.

Common questions

Do I need to pay to use Mapnostics?

No. Billing is not live yet. Settings → Plan shows your current plan and usage, and the Upgrade button is present but disabled — paid plans are coming, not yet enforced.

What are the pricing tiers I see on the landing page for?

They describe what each tier will include once billing ships. Until then, every account runs against the limits set in Settings → Plan regardless of the tier shown on the pricing page.

Will I be charged automatically when billing launches?

No account will be charged without a separate, explicit opt-in when the feature ships. Nothing about today's usage enrolls you in a future charge.

Talk to us →

Or start on the free tier first: analyze a repo →