Skip to content

connectsoft.io Domain Strategy

This document defines the strategy for connectsoft.io as the marketplace + ready-to-use SaaS solutions hub, including subdomain strategy. It is written for marketing, product, GTM teams, and anyone creating content for the .io domain.

connectsoft.io is the product & marketplace face: where customers see and buy/use actual SaaS applications built with the Factory. It's more commercial and product-centric than .ai.

Note

Marketplace Vision: .io may eventually host a full marketplace (templates, modules, maybe partner offerings). The marketplace will enable customers to discover, evaluate, and adopt ConnectSoft products and partner solutions.

Role of connectsoft.io

connectsoft.io is the marketplace + ready-to-use SaaS solutions hub. It represents:

  • Product Catalog - Ready-made SaaS platforms and solutions
  • Marketplace - Templates, modules, partner offerings (future)
  • Customer-Facing - Where customers discover, evaluate, and use products
  • Commercial - Pricing, plans, use cases, case studies

Key Characteristics: - Data Plane - User data, traffic from customers - Product-Focused - Emphasizes ready-made solutions - Commercial - Pricing, plans, sales-oriented content - Customer-Centric - Focuses on customer outcomes and value

See: SaaS Platforms Business Model for platform business model.

See: Marketplace Strategy for marketplace strategy.

Marketplace and Product Catalog

Category Example Products (Conceptual)
Core Platforms Identity, Audit, Config, Bot (SaaS modes)
Vertical Solutions Employment Services SaaS, Audit Trail SaaS
Tools & Utilities Config server, monitoring add-ons, etc.
Partner Offerings Partner-built solutions (future)

User Experience

Browse Products: - Product catalog with categories and filters - Product pages with features, pricing, use cases - Comparison tools and recommendations

See Pricing: - Pricing tiers and plans - Feature comparison tables - ROI calculators and cost estimates

Click Through to Subdomains: - Each product has its own subdomain (e.g., audit.connectsoft.io) - Product-specific landing pages and UIs - Seamless navigation between catalog and products

See: Product Portfolio Overview for product catalog.

Subdomain Strategy for SaaS Solutions

Subdomain Patterns

Subdomain Pattern Usage Example
<product>.connectsoft.io Public SaaS app landing/portal audit.connectsoft.io, identity.connectsoft.io
<product>-admin.connectsoft.io Admin/backoffice for that product audit-admin.connectsoft.io (optional)
<tenant>.<product>.connectsoft.io (optional) Tenant-specific apps sploot.audit.connectsoft.io (optional)

Product Subdomains

Core Platforms: - identity.connectsoft.io - Identity Platform SaaS UI - audit.connectsoft.io - Audit Platform SaaS UI - config.connectsoft.io - Config Platform SaaS UI - bot.connectsoft.io - Bot Platform SaaS UI

Vertical Solutions: - employment.connectsoft.io - Employment Services SaaS - Future vertical solutions as needed

See: DNS Subdomain Map for complete subdomain mapping.

Important

Naming Rules: 1. Use lowercase, hyphen-separated names for products 2. Use clear product names (audit, identity, config, employment) 3. Avoid ambiguous names or TLD misuse 4. New product subdomains must be approved by platform owner (Dmitry) 5. Update DNS Subdomain Map when new public subdomains are created

Target Audiences and Journeys

Audiences

  • Business Stakeholders - Product leaders, business owners evaluating SaaS solutions
  • Product Owners - Product managers looking for ready-made platforms
  • Buyers - Decision-makers evaluating ConnectSoft products
  • Existing Customers - Customers logging into SaaS applications

User Journeys

Journey 1: Discover Product → Understand Value → Start Trial

  1. Discovery: User finds product via search, referral, or catalog browsing
  2. Evaluation: Reviews product page, features, pricing, use cases
  3. Trial: Starts trial or requests demo
  4. Adoption: Signs up and begins using product

Journey 2: Existing User Signs In and Manages Environment

  1. Login: User logs into product subdomain (e.g., audit.connectsoft.io)
  2. Dashboard: Accesses product dashboard and features
  3. Management: Manages settings, configurations, integrations
  4. Support: Accesses support, documentation, resources

Journey 3: Marketplace Discovery

  1. Browse: User browses marketplace catalog
  2. Compare: Compares products, features, pricing
  3. Select: Selects product or solution
  4. Deploy: Deploys or integrates selected solution

Relationship to connectsoft.ai and connectsoft.dev

Domain Relationships

.ai → .io: - .ai explains WHY (Factory story, architecture, vision) - .io shows WHAT (ready-made products you can use/buy) - Cross-link: "See examples of ready-made platforms → connectsoft.io"

.io → .ai: - .io shows products built with the Factory - .ai explains how the Factory works - Cross-link: "Built on ConnectSoft AI Factory → connectsoft.ai"

.io → .dev: - .io shows products and use cases - .dev provides HOW (integration guides, APIs, SDKs) - Cross-link: "Developer docs → connectsoft.dev"

Tip

Cross-Linking Best Practice: Always link back to .ai for "built on ConnectSoft AI Factory" story. This helps customers understand the underlying technology and differentiates ConnectSoft from competitors.

Guardrails and Non-Goals

What .io Should Not Host

  • Deep Architecture Explanation - That's .ai (link to .ai for Factory story)
  • Low-Level SDK/API Docs - That's .dev (link to .dev for technical docs)
  • Raw Technical Documentation - That's .dev (link to .dev for detailed docs)

Risks to Avoid

Warning

Risk 1: Mixing Marketing and Operational UIs - Don't mix marketing pages with operational UIs on the same subdomain - Use separate subdomains/paths (e.g., www.connectsoft.io for marketing, audit.connectsoft.io for app) - Keep marketing and operational content clearly separated

Warning

Risk 2: Duplicating Content from .ai - Don't duplicate Factory story from .ai on .io - Link to .ai for Factory explanation - Keep .io focused on products and marketplace

Warning

Risk 3: Over-Complicating Navigation - Don't create complex navigation between products - Use clear product subdomains - Keep navigation simple and intuitive