← Mira AI
Front #6 · Config by conversation Q4 2026 · Roadmap preview

Change the platform
by asking for the change.

"Add a hotspot plan called Beach Day, 3 hours, AED 15, visible only to Marina Cafe." Mira drafts the change, shows you the diff, waits for your approval, then applies it. No form. No menu-diving.

trafyx.ai / config-chat
Preview mode
Add a hotspot plan called Beach Day, 3 hours, AED 15, visible only to Marina Cafe tenant.
Here's the change I'll make. Nothing is written yet — approve to apply.
// Diff · plans table · +1 row
+ INSERT INTO plans (name, plan_type, duration_hours, price_aed) VALUES
+ ('Beach Day', 'hotspot', 3, 15);
// Diff · price_book_items · +1 row (visibility)
+ INSERT INTO price_book_items (book_id, plan_id, is_visible) VALUES
+ ('marina-cafe-book', <new_plan_id>, true);
// Diff · all other price_books · plan hidden by default
(5 other books unchanged — visibility defaults to false)
Scoped to config, not code

What she can change.

Same whitelisted-action pattern. No arbitrary SQL. Every change gets a diff preview and an audit note.

Plans

Create, price, duration, FUP thresholds, activate/deactivate, hide/show per book.

Price books

New books, plan overrides, reseller assignments, visibility toggles.

Dunning rules

Grace thresholds, notification cadence, per-plan overrides.

Tenants (WaaS)

Onboard, SSID mapping, brand tokens, default plan.

NAS devices

Register, secret rotation, threshold overrides, device class assignment.

Notifications

SMS/email templates per tenant, escalation routing, quiet hours.
Every change is reversible

Diff in. Diff out. Always.

Every config change Mira applies is logged with its reverse-diff, so undo is one click. If Beach Day turns out to be a bad idea by Friday afternoon, "Mira, roll back the Beach Day plan" gets you back to Thursday morning.

The pattern extends

Same pattern. Sixth surface.
Landing Q4 2026.

Get early accessBack to Mira