Skip to main content

October 14, 2026

We've rebuilt the engine room and taught it to handle the small stuff on its own. Every part of Dalgo now lives, travels, and deploys together — and schema changes that are safe to accept no longer need anyone to wave them through.

One Codebase, One Shipment​

All of Dalgo — the backend, the webapp, the data pipelines, the AI service — now lives in a single repository and ships as a single coordinated release.

  • Everything moves together — the backend and the webapp are always in sync. No more cases where a backend update arrived before the frontend was ready for it.
  • One set of tests, all services — before any update ships, every part of the platform runs its test suite together. A failure in one stops the whole release, not just that service.

Containerised Deployment​

Dalgo now runs entirely in Docker containers.

  • Consistent everywhere — the container you run in testing is exactly the container that lands in production. No more environment-specific surprises.
  • Faster restarts — updates swap in a new container in seconds rather than minutes.
  • Easier to host — for NGOs or partners who self-host Dalgo, getting it running now takes a docker compose up rather than a manual environment setup.

Schema Changes Can Now Accept Themselves​

When a data source adds a new field — a new question in a KoboToolbox form, a new column from your CRM — Airbyte detects the change and has historically asked someone to approve it before syncing resumes.

  • Toggle it on once — under Settings → Data → Connections, flip the switch for auto-accepting non-breaking schema changes.
  • New columns arrive on their own — additions and other changes that won't break your existing pipelines are approved automatically, so syncs keep running without anyone needing to log in and click approve.
  • Breaking changes still need you — anything that would remove or rename a field that your pipelines depend on still surfaces for manual review. The automation only handles the safe ones.

Automated Delivery to Production​

Shipping a new version of Dalgo is now a single button.

  • One-click deploy — a release is triggered from GitHub, builds all services in parallel, and pushes them to production automatically.
  • Tests gate every deploy — nothing reaches production unless all four services pass their CI checks first.
  • Rollback is fast — because every release is a tagged container image, reverting to the previous version takes under a minute.

Release tag: 2.0.0