iveo 2.0 is here: the platform, rebuilt from the ground up

Today we’re switching on iveo 2.0 for everyone.

It’s a rebuild. New architecture, new database, new interface, new hosting. The old platform is switched off. Anyone signing in at app.my-iveo.de now lands in 2.0, with the same credentials as before.

What follows is the complete list. Nine chapters, sorted by area. Short on time? Read the first three.

1. Real time and the foundation

Most things are live. When a colleague moves a programme item, you watch it move. When someone publishes a speaker, the status changes on your screen without you doing anything. That goes for programmes, people, organisations, the calendar and publish status. An avatar stack at the top of the event shows you who’s working right now.

Underneath sits the foundation. Hosting, database, sign-in, real-time sync and file storage run in Frankfurt. Transactional mail goes through a tenant with its data region set to Europe, and AI inference runs through Frankfurt as well. The only piece outside the EU is the CDN cache for static assets. Database content never lives there.

Permissions apply twice. Once in the interface, once in the database row itself. A role never gets to see data it isn’t entitled to, whichever way it asks. You can override the defaults globally and per event.

Also new in the foundation:

• ⌘K opens a command palette anywhere. It searches programme items, people and organisations, always within your permissions.
• Archive instead of delete. Programme items, people, stages, organisations, guests and series go to the archive, and you bring them back from there. Archived items drop off the public website automatically.
• A message centre for direct messages within the team. Write to the iveo team and it becomes a support ticket on its own.
• The AI assistant sits as a tab in the same window. It creates events, stages, programme items, people and organisations, imports files, does research and cleans up duplicates. It acts under your identity and with your permissions, never beyond them.

2. Programme and submissions

The programme has always been the heart of iveo. In 2.0 it’s a calendar you touch directly.

You create stages and programme items and drag them into place in the day, week or stage view. Change the length: drag the edge. Landed in the wrong spot: undo. Blockers such as lunch break, press slot or locked time are pure calendar objects, and you can lock any entry so nobody moves it by accident. Shape and colour tell you at a glance whether a tile is a programme item, a submission or a blocker.

A programme item’s detail page is made of cards: header, time and place, description, classification. Then people and organisations with role, attendance type and speaking time, language interpretation, agenda items with tools and materials, videos. Programme types, formats, tags and categories are yours to define per event.

The call for papers is entirely new. Submitters get a public multi-step wizard with your info text on every step. You decide per field whether it’s visible or required, add your own custom fields and choose between your own and inherited branding. The deadline ends at the end of the day in the event timezone. After submitting, people confirm their address via double opt-in and receive an edit link to update their own proposal.

On your side, the review queue is waiting. Table, list or gallery, your call. You assemble the columns yourself from 24 fixed fields plus one per custom field, change width and order, and save named views that follow you to every device. Status, category and notes change inline. Three KPI tiles and a full CSV export come with it.

Two shortcuts: submissions can be auto-assigned to free slots via an availability heatmap, and a submission becomes a programme item with one click, fields pre-filled. A blocker converts into a programme item the same way, or duplicates to the next day.

If you produce the same conference every year, clone the series for the next edition. Sub-events hang under a global umbrella event and inherit its dates.

3. People and organisations

Each event has a person directory with salutation, name, title, rich-text bio, languages and photo upload. iveo checks formats and sizes as you upload. You switch between list, table and gallery views, search, sort, show archived entries and see per person whether they’re published. Their page lists every programme assignment with date, title, role and attendance type.

Organisations are assigned per event as host, co-host, sponsor or partner. Each can be created, edited, archived, restored and published individually. Organisation master data is global, which is why a sponsor looks the same across all your events.

iveo spots duplicates among people and organisations on its own. You pick the record that stays. Every reference moves over, the other records go to the archive.

4. Guests and registration

You switch the guest module on per event. While it’s off, the guest list simply doesn’t exist for your team.

Switched on, you get a list with on-site, virtual or hybrid attendance, RSVP status, source, notes and an optional link to one of the event’s speakers. KPI tiles sit above it: totals, on-site versus virtual, RSVP state, capacity. You send invitations per row by email. Or you generate a standalone invitation link and share it wherever you like.

The public registration form needs no login. Bot protection and rate limiting are built in. You configure double opt-in, capacity cap, registration deadline, consent text, mail language and extras such as dietary requirements, arrival window, job title and plus-one. Through a magic link, guests manage or cancel their own registration.

One detail we cared about: confirmation mails and CSV exports name the event timezone as city plus offset, say “14 Nov 2026, 20:00 (Tokyo, GMT+9)”. If the browser timezone differs, the form shows the visitor’s own time as well.

GDPR deletion of individual guests is deliberately a separate action in a separate place: it runs through the archive, not through the reversible archiving in the list.

5. Event website and publishing

The public event website reads from its own published dataset. Nothing appears before you publish it. Whatever you unpublish is gone immediately.

Branding covers your own font family via font upload, a six-value colour palette with card transparency, corner logo, main logo, hero video and a reusable asset library. The hero background is mesh, solid, gradient or image with adjustable overlay, and the theme is light, dark or automatic.

The website editor shows a live preview beside the settings, with a desktop and mobile switch and the real page layout for every page. Three templates are ready: Classic, Conference and Custom. The Custom home page is a sortable block list of countdown, trailer, key numbers, topics in focus and speakers in focus. Each block hides itself while its data is missing. The partner logo bar is available in every template.

You can hide whole sections: programme, speakers, partners, about. They disappear from navigation, footer, sitemap and hero buttons, and their URLs redirect to the home page. That’s how you go live weeks before the programme is final.

The public pages at a glance: home, programme as list, cards, calendar and timeline with filters by stage, topic, programme type and format, programme detail, speaker gallery and profiles, organisations by role, personal favourites, about, imprint, search and your own CMS pages. The programme is also an iCal feed you can subscribe to.

You set up a custom domain with verification status and DNS instructions. You choose which languages visitors can switch to and which one is the default. Publishing works individually or in bulk, with a diff view and counters for pending, changed and up to date. The public site picks up the new state within about a minute.

On the timeline and calendar, a now line marks the current moment in the event timezone. Each page names its timezone exactly once, such as “All times in Istanbul (GMT+3)”.

6. Produce: show day

Produce mode turns the event into a cockpit for directors, operators and moderators.

In the live overview you pick a stage, see the running programme item and a preview of the next one, go live, stop, move on. Each programme item carries its speaker running order with photo, role, attendance type and speaking time, plus the agenda preview.

Take a stage live and the change reaches the public website and the screen graphics in under half a second.

The director view shows one timeline per day across all stages. A live header tells you what’s on air on each stage, and a now line moves along.

For projectors and streams there are two fullscreen outputs. Open the timeline in a second window or use its URL as a browser source in OBS, on foyer screens or on a projector. The lower-thirds studio lists every programme item within a ±48-hour window with status, number of speakers and languages with or without interpretation. One click, and the lower third stands as a fullscreen graphic. Both outputs follow programme, people and stage changes live, without a reload.

7. Team, roles and settings

Sign in with email and password, with a magic link or with Google. Password reset and token pages for team invitations and guest links are included.

You invite team members by email with a role. Open invitations show their expiry date and can be withdrawn. Which roles you may hand out follows the role hierarchy.

There are ten roles. Producers have full access including publishing, custom domain, merges and series. Below them organiser and editor, then the show-day roles operator, director and moderator. Guest managers see only the guest list. Then speaker and free user. A programme organiser sees only the programme items assigned to them.

The settings hub per event has tabs for general data, branding and media, team, guest rules, programme rules, publishing, submission rules and archive. Everyone sees the event timezone. Producers change it and decide whether all times move along or stay put. Programme-free days are picked by clicking days in a calendar popover.

Personal settings live in the user menu or behind ⌘K: profile and avatar, appearance, password, notifications for mentions and changes to programmes, organisations and people. New users get a three-step onboarding through exactly those items. Organisations are created at account level in the lobby. A new event starts via the wizard, with an import, with placeholders or empty.

8. Languages and accessibility

The interface comes in German, English and Arabic. Arabic runs right to left, throughout.

Per event you choose which languages the public website offers and which one is the default. At least one always stays active. Content languages are tracked separately, meaning the language programme items, people and submissions are written in. The language of registration and confirmation mails is set per event too.

Every user saves their own preferences: compact or full layout width, text size, reduced motion. The event website has a light, dark or automatic theme.

Times appear everywhere in the event timezone with city and offset. If your browser timezone differs, your own time sits next to it.

9. Public API and integrations

The REST API at /api/v1 is token-based, and the public OpenAPI document is the binding contract.

Read tokens return the event, organisations, stages, programme items with cursor pagination, speakers, agenda items and binary assets such as logos and photos. Write tokens create an event, change its name, dates and timezone, and invite people as producer or operator. That’s a deliberate springboard for agencies. The planning happens in the platform.

Tokens are only created inside the app. An admin enables API access, then you create the token under Settings → API.

The event inbox brings correspondence to where the event lives. Per event you connect one Google Workspace mailbox via OAuth and reply directly in iveo. Conversations, assignment to a producer, search across subject, sender and body, filters, auto-saved drafts, internal notes with @mentions, attachments, bulk actions. The iveo status mirrors back as a Gmail label. New mail shows up within seconds.

From the same dialog you send group mailings to the team by role, speakers, registrants or submitters. Templates save subject, body and groups.

And for getting started: in the event wizard you upload your programme as Excel, CSV or PDF. The AI assistant builds stages, programme items and speakers from it.

What this means for you

If you’ve used iveo before, sign in at app.my-iveo.de. Your credentials still work. The onboarding walks you through profile and settings once, and you’re in.

If you’re new: Get started. Create an empty event, import a programme or have a look around a placeholder event first.

The Docs have been moved to 2.0. If something is missing or behaves differently from what you expect, write to us. What comes next is on the roadmap.

Thank you to everyone who walked this road with us.