Semantico

Powerful semantic alerts and notifications for your databases

Get Started View on GitHub

Why Semantico?

Semantico is a .NET library that transforms database monitoring with semantic queries, flexible alerting, and cross-database orchestration.

  • Multi-Database Support: PostgreSQL, SQL Server, and MySQL in one unified platform
  • Flexible Alerting: Email, Microsoft Teams, and Jira notifications with cron scheduling
  • Query Chaining: Multi-step queries with cross-project and cross-database capabilities
  • Full Results as Attachments: Email notifications include complete datasets as CSV for Excel analysis
  • NuGet Integration: Add to your ASP.NET Core application in minutes
  • Blazor Admin UI: Modern, responsive UI for managing queries and subscriptions
  • Schema-Agnostic: Multi-tenant support with runtime schema configuration

🏗️ System Architecture

Semantico follows Clean Architecture principles with clear separation of concerns:

graph TB
    subgraph UI["Presentation Layer"]
        BlazorUI[Blazor UI Components<br/>MudBlazor]
    end

    subgraph Core["Application Services Layer"]
        QuerySvc[Query Service] ~~~ SubSvc[Subscription Service] ~~~ MigSvc[Migration Service]
        NotifSvc[Notification Service] ~~~ DataSrcSvc[DataSource Service] ~~~ MetaSvc[Metadata Service]
    end

    subgraph Adapters["Notification Adapters"]
        EmailAdapter[Email Adapter] ~~~ TeamsAdapter[Teams Adapter] ~~~ JiraAdapter[Jira Adapter]
    end

    subgraph Data["Data Access Layer"]
        EFCore[Entity Framework Core<br/>SemanticoContext] ~~~ Dapper[Dapper<br/>Metadata Queries]
    end

    subgraph Infrastructure["Infrastructure Layer"]
        PgSQL[(PostgreSQL)] ~~~ MSSQL[(SQL Server)] ~~~ MySQL[(MySQL)]
        Scheduler[Job Scheduler<br/>via ISemanticoScheduler] ~~~ SQLiteVM[SQLite Virtual Tables<br/>Cross-DB Joins]
    end

    BlazorUI --> Core
    Core --> Adapters
    Core --> Data
    Data --> Infrastructure
    Core --> Infrastructure
    Adapters --> Infrastructure

    style UI fill:#e3f2fd
    style Core fill:#f3e5f5
    style Adapters fill:#fff3e0
    style Data fill:#e8f5e9
    style Infrastructure fill:#fce4ec

Query Execution Flow

Multi-step queries with cross-database capabilities:

sequenceDiagram
    participant User
    participant Scheduler
    participant QueryOrchestrator
    participant VirtualTableManager
    participant PostgreSQL
    participant SQLServer
    participant MySQL
    participant NotificationService
    participant Adapter

    User->>Scheduler: Create Subscription (Cron)
    Scheduler->>QueryOrchestrator: Execute Query (Scheduled)

    QueryOrchestrator->>PostgreSQL: Execute Step 1
    PostgreSQL-->>QueryOrchestrator: Result Set 1
    QueryOrchestrator->>VirtualTableManager: Store @@result1

    QueryOrchestrator->>SQLServer: Execute Step 2 (with @@result1)
    SQLServer-->>QueryOrchestrator: Result Set 2
    QueryOrchestrator->>VirtualTableManager: Store @@result2

    QueryOrchestrator->>VirtualTableManager: Execute Final Query<br/>(JOIN @@result1 and @@result2)
    VirtualTableManager->>VirtualTableManager: Create SQLite Virtual Tables
    VirtualTableManager-->>QueryOrchestrator: Combined Results

    QueryOrchestrator->>NotificationService: Send Results
    NotificationService->>Adapter: Dispatch (Email/Teams/Jira)
    Adapter-->>User: Notification Delivered

Data Migration Flow

ETL orchestration with multiple migration modes:

flowchart LR
    subgraph Source["Source Extraction"]
        Q1[Query Step 1<br/>PostgreSQL]
        Q2[Query Step 2<br/>SQL Server]
        Q3[Query Step 3<br/>MySQL]
    end

    subgraph Transform["Transformation"]
        VT[Virtual Tables<br/>Cross-DB Join]
        Enrich[Data Enrichment<br/>Business Logic]
    end

    subgraph Load["Load Operations"]
        Insert[Insert Only<br/>New Records]
        Upsert[Upsert<br/>Insert + Update]
        Truncate[Truncate Load<br/>Full Refresh]
        Sync[Sync Delete<br/>Perfect Mirror]
    end

    subgraph Destination["Destination"]
        Target[(Target Database<br/>Any Engine)]
    end

    Q1 --> VT
    Q2 --> VT
    Q3 --> VT
    VT --> Enrich
    Enrich --> Insert
    Enrich --> Upsert
    Enrich --> Truncate
    Enrich --> Sync
    Insert --> Target
    Upsert --> Target
    Truncate --> Target
    Sync --> Target

    style Source fill:#e3f2fd
    style Transform fill:#f3e5f5
    style Load fill:#fff3e0
    style Destination fill:#e8f5e9

Use Cases

🚨 Data Validation Alerts

Problem: Developers need to ensure data meets business rules and catch data quality issues early

Solution: Create queries that trigger alerts when data is invalid, missing, or violates constraints - such as orphaned records, null required fields, or invalid state combinations. Also used by DBAs for database health metrics (table size, connection count, replication lag).

Benefits: Early detection of data issues, automated data quality checks, prevent invalid states from reaching production

Learn more about alerting →

📊 Scheduled Reports with Attachments

Problem: Teams need automated reports delivered regularly without manual SQL execution

Solution: Schedule queries with cron expressions and receive full results as Excel/CSV attachments via email. Perfect for daily sales reports, weekly analytics, or monthly summaries delivered directly to stakeholders.

Benefits: Zero-touch reporting, full dataset delivery, Excel-ready format, automated scheduling

Learn more about notifications and attachments →

🔄 Data Migration Orchestration

Problem: Development teams need auditable data migration tracking across environments

Solution: Data migration jobs with execution history, validation checks, and error tracking

Benefits: Compliance audit trail, repeatable workflows, error visibility

Learn more about data migrations →

Quick Start

Add Semantico to your ASP.NET Core application in under 30 minutes:

1. Install NuGet Packages 

dotnet add package Semantico.Core.PostgreSql
dotnet add package Semantico.UI.AspNet

2. Configure in Program.cs 

using Semantico.Core;
using Semantico.UI.AspNet;

// Add Semantico with PostgreSQL (single method call)
builder.Services.AddSemantico(builder.Configuration, options =>
{
    options.UsePostgreSql(builder.Configuration.GetConnectionString("SemanticoContext")!, "semantico");
    options.AddSemanticoScheduler<YourHangfireScheduler>();
});

var app = builder.Build();

app.UseStaticFiles(); // Required for Semantico UI assets

// Configure UI
app.UseSemanticoUI()
    .UseBasicAuthentication("admin", "admin")
    .AddBlazorUI("/semantico");

3. Add Connection String

appsettings.json:

{
  "ConnectionStrings": {
    "SemanticoContext": "Host=localhost;Database=semantico;Username=postgres;Password=yourpassword"
  }
}

4. Run Application 

dotnet run

Access Semantico UI at http://localhost:5000/semantico

View detailed quick start guide →

Features

Core Capabilities

Advanced Features

Documentation

🚀 Getting Started

New to Semantico? Start here to add Semantico to your application.

📖 Features

Explore all capabilities with detailed guides and examples.

🔧 Advanced Topics

Power user scenarios and extensibility patterns.

💬 Support

Get help and contribute to the project.

Key Features at a Glance

Feature Description
Multi-Database Connect to PostgreSQL, SQL Server, MySQL
NuGet Package Easy integration into ASP.NET Core applications
Cron Scheduling Flexible execution timing with cron expressions
Multi-Step Queries Chain queries with result aggregation
Cross-Database Query multiple databases in single workflow
Notifications Email (with CSV attachments), Teams, Jira delivery
Full Dataset Attachments Email includes complete query results as CSV (unlimited rows)
Parameters Dynamic query values with placeholders
User Management Built-in users, roles, JWT/OAuth, first-run setup
Admin Settings Runtime config, hot-swap LLM providers, audit trail
Schema-Agnostic Multi-tenant deployments with runtime schema selection
Execution History Complete audit trail of all executions
Blazor UI Modern admin interface with MudBlazor

Requirements

  • .NET 9.0 or later
  • ASP.NET Core web application
  • PostgreSQL 12+ or SQL Server 2019+ for Semantico metadata
  • Job scheduler implementing ISemanticoScheduler (e.g., Hangfire, Quartz.NET, or custom)
  • (Optional) Email provider for email notifications (SMTP, etc.)

Community and Support

Built for .NET developers who need powerful database monitoring and alerting