Was kommt zu svoxx

Isolated experiences per domain — each portal with its own branding, configuration, and roles while sharing the svoxx core.

Configure listing types, action types, and workflow automations so buyers and providers move from discovery to delivery in one system.

One identity across the network with secure sessions, email verification, and common profile primitives.

Billing hooks and plan infrastructure so each portal can offer membership, listing plans, and hosted checkout where enabled.

Site config, content surfaces, SEO helpers, and analytics so operators can run their portal without a separate stack.

More built-in steps between handoff, revisions, and completion — with notifications that keep every party in sync.

Ziel: H1 2026

System-aware and manual theme controls across public marketing and signed-in app shells.

Ziel: Q1 2026

Authenticated APIs for orgs that want to sync listings, webhooks for workflow state, and read-only embeds for partners.

Ziel: H2 2026

Shared seats, role-based access within a company, and handoff of listings between teammates.

Ziel: H2 2026

Layered reviews, completion history, and dispute resolution hooks surfaced where transactions happen.

Ziel: 2026

Faster language packs and locale-aware content for more regions without forking each portal.

Ziel: 2026

Suggestions that use privacy-preserving activity signals to help users find the right portal, listing, or partner.

A structured path for agencies and communities to launch and operate their own vertical on svoxx with shared best practices.

Add-on tooling for data residency, export, and audit where enterprise buyers require it.