DMCDMC Bilgi Teknolojileri

Transparent roadmap, updated monthly

Our commitment to customers: we openly share what we are building, what we plan, and what we are researching. This list is the customer-facing summary of our backlog (BL-XXX).

Now — Currently active Next — Coming 90 days Later — 6+ month research

Our development plan — 2026-Q2 / Q3 / Q4

✅ v1.7 yayınlandı (2026-05-26) — Grafana / DataDog / IDERA / RedGate parity backlog'unun TAMAMI
13 sprint tek release'de: Folder Organization + Versioning + Maintenance Windows + Quick Mute + Alert dedup + cascade snooze + Dashboard JSON I/O + PG/MySQL Plan Regression + Library Panels + Explore Mode + Transformations + Public Snapshot + QR + Smart Statistical Baseline (NumPy MAD 3σ — ML değil) + RBAC Granular (19 scope) + Mobile drawer. 126 unit test (108 backend + 18 frontend), 0 schema migration, agentless mandate korundu. Detay: changelog · docs/RELEASE_NOTES_v1.7.0.md

Now · Currently working on

2026-Q2 — May end / June — to be completed
  • BL-007 3rd-party penetration test aktif

    CREST/OSCP-certified InfoSec firm; report + remediation log. Mandatory for enterprise RFPs.

  • BL-008 Legal template attorney review aktif

    privacy/terms/cookies/sla/dpa — 5 pages pass attorney review; .legal-banner notice removed once approved.

  • BL-006 Frontend bundle optimization aktif

    SecurityCenterV2 191KB → route-based lazy load + bundle analyzer. Target LCP < 2.5s.

  • BL-005 Test coverage gate aktif

    pytest-cov + vitest coverage; CI gate at 70% minimum. Prerequisite for P1 modularization.

  • BL-031 PoC process page tamam

    site/poc.html + docs/POC_SURECI.md — what you are reading right now.

Next · Coming 90 days

2026-Q3 — July / August / September — to start
  • BL-009 Site screenshot library planned

    9 real screenshots for compliance/airgap/toolkit/install pages; builds trust before the demo.

  • BL-010 E2E tests (Playwright) planned

    30–50 critical-path tests (login → source → metric → alert → compliance → PDF). Regression coverage.

  • BL-011 Load + chaos test (200 instances) planned

    k6/Locust + chaos-mesh; continuous proof of the "200+ instances" claim. Public benchmark report.

  • BL-012 AI insights deepening (5 LLM tools) planned

    query rewriter + index suggester + plan explainer + anomaly narrator + blocking root-cause. LiteLLM tool calling.

  • BL-013/14 Backend modularization planned

    dynamic_collector.py (5.6 KLOC) and sqlserver.py (12.5 KLOC) split into modules. Lower maintenance cost.

  • BL-016 Webhook payload documentation planned

    Concrete payloads for Slack/Teams/PagerDuty/ServiceNow + Postman collection + sample handler.

  • BL-020 GraphQL API planned

    strawberry-graphql active; mirrors 80%+ of REST endpoints. For modern frontend teams.

Later · 6+ months (research / triggered by demand)

2026-Q4 and later — reference customer can trigger
  • BL-032 SaaS managed offering 2026-Q4 hedef

    DMC-managed SaaS — multi-tenant infrastructure (ARCH-003) is ready; remaining: tenant onboarding wizard + billing + shared Mongo cluster + tenant-aware backup.

    Duration: 6 weeks operational + 4 weeks beta + 2 weeks GA = 3 months. Triggered by customer demand.

  • BL-022 DataDog / New Relic migration path research

    "Try Sentinel before dropping Datadog" → two-way migration (metric push + source import).

  • BL-023 Mobile app (PWA / React Native) research

    Push notifications (FCM/APNs); see alerts from bed at night. PWA first phase is faster.

  • BL-024 Marketplace listings (Azure / AWS / GCP / AppSource) 2026-Q4 hedef

    Bring Your Own License model. Legal approval (BL-008) + pen-test (BL-007) are prerequisites.

  • BL-021 MongoDB sharded cluster research

    For 1000+ instance scenarios. Triggered when customer base reaches 100+.

  • BL-025 Public status page (uptime) planned

    status.sentineldb360.com — mandatory for SaaS customers. SLA service-credit transparency.

  • BL-027 Community / Discord / Forum research

    Central hub for the DBA Toolkit OSS community. MVP renewal + organic lead.

Transparency matters — we tell you what we are NOT doing too

For customer trust: we don't pretend to do what we're not. Items below were considered historically but are not in active planning.

DEFERRED

BL-019: Oracle support

Decision (2026-05-03): Sentinel is limited to 4 engines (MSSQL + PG + MySQL + MongoDB). Oracle is not planned.

  • Reason: DPA/SolarWinds dominate Oracle, low competitive advantage
  • Reconsider trigger: 3+ enterprise RFPs requiring Oracle
  • SQL Server is the dominant engine in Turkish regulated market (already covered)
Stratejik

OpenTelemetry exporter — under evaluation

Currently we have Prometheus; OpenTelemetry exporter can be added on customer demand. When the backlog item is opened, it moves to "Next".

We do what we say — our 3 principles

Principle 1

Site + Docs + Backlog all required

No feature is built without these three. Work done = marketed on site + documented + dated backlog item. No exceptions.

Principle 2

Monthly revision, transparent updates

Roadmap is revised at the start of every month. New features enter, completed ones leave, deferred ones marked. Timeline that protects customer trust.

Principle 3

Customer demand is the trigger

Items in Later usually move to Next when "first 3 customers want it" trigger fires. SaaS, Mobile, Marketplace listing — accelerated by demand.

Want a feature not in the list?

Tell us — it goes into backlog as a triggering customer demand. Pre-registration may give you early access.