DatoCMS vs ToolJet

The dated feed has been quiet since late April, when the CLI work landed — npx datocms running without setup, and OAuth-based project linking. The live change is undated in this feed: from 25 August, new projects lose the custom admin palette and get only the monochromatic system, which derives every colour from one hue at WCAG AA contrast. Existing projects keep what they have. April also raised the Developer Plan CMA limit, added a plugin scaffold to the starter kits, and turned on antivirus scanning for every Media Area upload.

The pattern across this window is DatoCMS narrowing the decisions it hands users, and doing it deliberately. Antivirus scanning became automatic rather than optional; the CLI stopped requiring setup; and now admin theming stops being freeform for new projects because editors reported that freeform produced unreadable interfaces. Each of those removes a configuration surface and replaces it with a guaranteed outcome, which is a defensible direction for a CMS whose users are editors rather than the developers who set the project up. The agent-facing work — the Remote MCP Server and Agent Skills — sits on the same axis, giving models a fixed interface rather than a configurable one.

Expect the monochromatic system to eventually reach existing projects too, since a quality bar that applies only to new ones leaves the reported problem in place wherever it already exists. When that happens, or whether it will, is not stated here.