eKuiper Manager v1.2.1

eKuiper Manager v1.2.1 turns the experimental application into an installable, self-hosted eKuiper operator stack.

Highlights

• Start Manager, official eKuiper 2.4.1, and a private PostgreSQL sidecar with one Docker Compose command.
• Use the context-aware operator assistant from every authenticated page, including the rule designer. Provider credentials stay server-side; page context is bounded and redacted; replies render safe Markdown and include clickable follow-up questions.
• Design rules visually, inspect generated SQL/JSON, validate, create stopped, and duplicate safely.
• Bootstrap an owner and manage the basic local user lifecycle: sign-in/out, add, reset, forced password change, and delete.
• Register, probe, select, and remove eKuiper nodes through a server-owned encrypted registry.
• Operate the audited eKuiper 2.4.1 contract across streams, tables, rules, connections, schemas, uploads, plugins, functions, services, metadata, and import/export.
• Browse the refreshed 98-path/140-operation Swagger contract on GitHub Pages.

Security and reliability

• Same-origin mutations, hashed sessions, scrypt passwords, encrypted node authorization, recursive response redaction, registered-target proxying, DNS/IP validation, redirect rejection, rate limits, audit events, and bounded request/response bodies.
• Non-root read-only Manager container with dropped capabilities and pinned production images.
• Checked PostgreSQL migrations, durable named volumes, health checks, restart persistence verification, 57 unit tests, eight local desktop/mobile journeys, clean-container CI, CodeQL, and zero npm audit findings.

Upgrade note

This release replaces the former experimental browser/SQLite/Prisma/EMQX/Supabase paths. Back up first. Compose deliberately ignores legacy DATABASE_URL=file:...; use the bundled PostgreSQL sidecar or explicitly set MANAGER_DATABASE_URL.

The optional assistant is off by default. See docs/AI_ASSISTANT.md for provider configuration and its data boundary.