Keep relationship context current
Unify company, person, lead, activity, opportunity, campaign, and quote records so teams do not lose context between handoffs.
Sovereign CRM for customer relationships, pipeline control, and AI-era sales work.
Nodus gives sales, account, and leadership teams a European-controlled CRM for leads, accounts, contacts, opportunities, activities, pipelines, forecasts, campaigns, quotes, reporting, and AI-assisted relationship work.
CRM data contains customer identities, contact history, revenue forecasts, deal strategy, lead sources, consent records, and commercial notes. When this data lives across spreadsheets, inboxes, generic SaaS tools, and disconnected pipeline boards, teams lose context and compliance teams inherit unnecessary exposure.
Nodus combines account and contact management, lead lifecycle workflows, opportunity pipelines, activity tracking, campaigns, quotes, forecasts, reports, global search, dashboard metrics, chat surfaces, and an MCP server into one CRM platform built for tenant-aware customer operations.
Nodus is positioned to make customer relationships more visible, revenue forecasts more defensible, and sensitive CRM data easier to govern.
Unify company, person, lead, activity, opportunity, campaign, and quote records so teams do not lose context between handoffs.
Review stages, probability, owner, value, expected close date, next step, weighted value, and at-risk deals from shared pipeline data.
Track lead source, score, rating, qualification, disqualification reason, and conversion into account, contact, and opportunity records.
Record calls, emails, meetings, tasks, notes, priorities, owners, due dates, completion state, summaries, and action items.
Use European-controlled deployment patterns, Keycloak identity, Kubernetes workloads, tenant-scoped records, and secrets held outside git.
Expose CRM tools through MCP and chat APIs while keeping customer data, search, lead conversion, opportunities, and activities inside controlled service boundaries.
Create or import leads, accounts, contacts, owners, source attribution, tags, custom fields, consent details, segments, territories, and relationship mappings.
Qualify or disqualify leads, convert promising leads, create opportunities, move deals through pipeline stages, update next steps, and close deals as won or lost.
Use dashboards, pipeline boards, reports, global search, activities, automation/scoring models, chat routes, and MCP tools to keep the CRM actionable.
Manage companies with type, industry, website, revenue, employee count, addresses, parent account, owner, segment, territory, health, engagement, tags, and custom fields.
Track people with account links, role, title, department, email, phone, lifecycle stage, contact preferences, language, timezone, consent, scores, tags, and activity timestamps.
Capture leads with source, campaign, UTM context, score, rating, owner, qualification state, disqualification reason, and conversion links.
Convert a qualified lead into account, contact, and opportunity records while stamping conversion state and preserving source context.
Manage deals with account, amount, currency, recurring value, pipeline, stage, probability, forecast category, close date, next step, owner, competitors, win/loss state, and AI fields.
Display stages and open opportunities grouped by stage, with stage probability and weighted pipeline summary views.
Record calls, emails, meetings, tasks, and notes with related CRM entity, owner, assignee, due date, timing, status, priority, call/email/meeting metadata, summaries, and action items.
Model campaigns, lead sources, campaign costs, responses, conversions, revenue, members, and source attribution for sales and marketing handoff.
Track products, opportunity products, quotes, quote items, territories, territory members, forecasts, quotas, pipeline values, commit values, and AI forecast factors.
Use global search, dashboard KPIs, pipeline summary, sales forecast, activity summary, lead conversion reports, and MCP tools for CRM search, records, lead conversion, pipeline, and activity operations.
Nodus is implemented as a Go CRM API, a Next.js CRM UI, and a Go MCP service running in Kubernetes, backed by PostgreSQL CRM tables and Keycloak-based authentication.
Manage long-cycle opportunities, stakeholders, account history, lead qualification, pipeline stages, and forecast reviews.
Maintain customer health, engagement, contact lifecycle, relationship history, activities, next steps, and renewal or expansion opportunities.
Preserve lead source, UTM data, campaign attribution, lead score, qualification state, and conversion records.
Track relationship-driven revenue, referral sources, activities, opportunities, proposals, and account context across long nurture periods.
Keep customer relationship data in a European-controlled operating model with identity, role controls, soft deletes, and audit-friendly record structure.
Let authorized assistants search CRM data, create records, qualify leads, move opportunities, close deals, and complete activities through MCP tools.
Nodus is built to connect sales data, identity, AI assistance, workflow automation, reporting, and Kubernetes operations inside the GoSec/Vianordis platform.
Keeps access tied to organization accounts, roles, and sign-in policy.
Keeps access tied to organization accounts, roles, and sign-in policy.
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Stores structured service records in a controlled tenant-aware backend.
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Lets approved systems connect without ad hoc exports or manual copy-paste.
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Lets approved systems connect without ad hoc exports or manual copy-paste.
Powers AI features while keeping model execution inside the controlled environment.
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Lets approved systems connect without ad hoc exports or manual copy-paste.
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Nodus handles sensitive commercial data: customers, contacts, consent, communication records, deal value, forecasts, and AI-assisted relationship context. Its implementation combines identity, roles, tenant fields, database consistency checks, and controlled deployment boundaries.
Keycloak-protected API and UI authentication paths
Admin, operator, user, and auditor role groups for read, write, delete, and admin actions
Core CRM tables carry tenant_id and tenant-scoped query patterns
Database trigger prevents contacts from linking to accounts in another tenant
Database trigger validates CRM owners belong to the same tenant
Deleted timestamps preserve audit-friendly lifecycle state for core CRM records
Trigram indexes for fuzzy account, contact, and CRM search workflows
API server-level request limiting for protected service routes
HTTPS MCP service with Keycloak validation and optional client-certificate trust path
Database, Keycloak, TLS, and API secrets referenced by name and provisioned outside git
Nodus pricing should reflect number of users, tenants, records, integrations, AI/MCP usage, data migration scope, reporting needs, support expectations, and whether the deployment is managed, private, or customer-controlled.
Nodus is for B2B sales, account management, marketing operations, professional-services, and regulated customer-facing teams that need a sovereign CRM.
The product model covers leads, accounts, contacts, opportunities, activities, campaigns, products, quotes, relationships, territories, forecasts, interactions, scoring rules, automation rules, and integrations.
Yes. The API and MCP surfaces include lead qualification, disqualification, and conversion into account, contact, and opportunity records.
Yes. Nodus includes pipeline stages, probabilities, pipeline summary views, and a board endpoint/UI surface for open opportunities grouped by stage.
The API exposes pipeline summary, sales forecast, activity summary, and lead conversion reports, along with dashboard metrics and CRM search.
Activities can represent calls, emails, meetings, tasks, and notes, with owners, assignees, due dates, status, priority, related CRM entities, call/email/meeting metadata, summaries, and action items.
Yes. The app includes chat API surfaces and a dedicated MCP server with tools for dashboard, search, accounts, contacts, leads, opportunities, activities, lead conversion, stage movement, and pipeline listing.
Nodus uses Keycloak authentication and CRM role groups for read, write, delete, and admin operations. The MCP service validates Keycloak tokens and can also use a configured mTLS service-auth path.
No. The inspected deployment notes show the public product is Nodus, while some live service names, hostnames, database references, and Keycloak clients still use CRM-era identifiers until a deferred cutover.
Yes. The app includes Kubernetes manifests for API, UI, and MCP workloads, plus deployment notes for namespace, services, internal ingresses, TLS, and out-of-band secrets.
Use Nodus to manage leads, accounts, contacts, opportunities, activities, reports, forecasts, and AI-assisted CRM workflows without giving up control of customer data.