Bring the history in your tools into Fortiana.

Connect the tools your team uses. Fortiana builds memory from their conversations, documents, and activity, so answers can draw on more than one source.

Browse integrations

No single source has the whole story.

A request arrives by email. The plan is in a document, tasks are in Jira, and the discussion is in Slack. Fortiana connects these records while keeping each one tied to its source.

Memory built
Context and sources preserved
Who did what, when, and how it connects
Your toolsAdditional sources
What happened the last time we raised prices?
Compiled in2s7 sourcesStripe, Salesforce, Gmail, Zendesk, Slack, Google Drive, Notion

The price increase generated €84,000 in additional revenue in the first three months. It also led to 47 cancellations, 32 of them from customers who received less than 30 days’ notice.

Most customers whose price changed at renewal did not cancel. The review recommended giving existing customers 45 days’ notice and applying the new price at renewal. Neither recommendation is included in the current plan.

What should we carry forward this time?

Apply the new price immediately to new customers only. Give existing customers 45 days’ notice and apply the new price at renewal.

Last time, support volume started to spike two days after the announcement, so schedule extra support staff for the first week.

Codex~/dev/dashboardgpt-5.6-sol · high
Build the workspace usage dashboard with date filters, KPI cards, a weekly usage chart, and a recent activity table. Reuse the existing design system and verify mobile and desktop.
I’ll stage the project context, then inspect the mapped files before editing.
Called fortiana.stage_context({"task":"workspace usage dashboard","scope":"apps/web"})
16 linked sources · 8 relevant files [map] dashboard-shell.tsx — layout and state boundaries [map] usage-query.ts — date range and aggregation contract [map] metric-card.tsx — existing KPI composition [map] chart.tsx — owned chart contract … +4 related files [reuse] Card · Tabs · Select · ChartContainer · Table · Badge · +2 components [decision] UsageQuery owns date-range normalization. [history] Previous chart used raw colors and omitted the empty state. [verify] 390 / 768 / 1440 · loading / empty / populated · +4 checks
Explored
Read apps/web/src/features/usage/dashboard-shell.tsx
Read apps/web/src/features/usage/usage-query.ts
Read packages/ui/src/metric-card.tsx
Read packages/ui/src/chart.tsx
I’ll implement against the existing query and component contracts, then add focused state coverage.
Edited apps/web/src/features/usage/dashboard-shell.tsx(+2 -1)
12import { WorkspaceUsageDashboard } from "./workspace-usage-dashboard";
42 <UsageDashboardPlaceholder />
42 <WorkspaceUsageDashboard />
Edited apps/web/src/features/usage/workspace-usage-dashboard.tsx(+118 -0)
Edited apps/web/src/features/usage/usage-metrics.tsx(+62 -0)
Edited apps/web/src/features/usage/usage-chart.tsx(+87 -0)
Edited apps/web/src/features/usage/recent-activity-table.tsx(+53 -0)
Edited apps/web/src/features/usage/usage-dashboard.test.tsx(+48 -0)
Ran pnpm exec vitest run apps/web/src/features/usage/usage-dashboard.test.tsx && pnpm typecheck
✓ apps/web/src/features/usage/usage-dashboard.test.tsx (18 tests) … +4 lines (ctrl + t to view transcript)

Built the workspace usage dashboard across six files, reusing the existing query and UI contracts.

Focused tests and pnpm typecheck pass.

─ Worked for 4m 12s

Import history. Keep memory up to date.

Native connectors can import past records and receive later changes. Available data and update behavior vary by service. For file imports, add a newer export to include later changes.

Memory growth

326.8k52.7%

Last 30 days

Connected data sources and their current states
AuthenticationActions
Slack
Ready
OAuthConnected
14.6k2 min ago
Google Drive
Syncing78%
OAuthConnected
38.4kNow
Jira
Ready
API tokenExpires in 24 days
12.1k4 min ago
ChatGPT
Ready
Compliance APIExpires in 18 days
6.7k3 min ago
GitHub
Ready
GitHub AppConnected
31.6k11 min ago
Salesforce
Paused
OAuthReconnect required
8.2k6h ago
Microsoft Teams
Ready
OAuthConnected
21.2kNow
Notion
Ready
OAuthConnected
18.9k2 min ago
Dropbox
Ready
OAuthConnected
9.4k4 min ago

Not every source connects the same way.

The connection method depends on the system and whether you need ongoing updates.

Native connectors

Connect services such as Slack, Gmail, and Jira directly to Fortiana.

Imports

Use exported conversations, files, and datasets without a live connection.

Custom connections

Use an API integration for an internal tool or specialized system.

Access rules still apply.

Connecting a source doesn’t make its contents available to everyone. Answers only use information the person asking is allowed to access.

Find the integration you need.

Browse supported sources to see what each integration can import and how it connects to Fortiana.

Browse integration directory
  • Slack
  • Google
  • Atlassian
  • GitHub
  • Microsoft
  • GitLab
  • HubSpot
  • Salesforce