Give each AI teammate the engine that fits the job. Claude, GPT, Gemini, Grok, open models, and custom agents can work from one Space context, with no single-provider lock-in.
Lydo separates the role from the model. Your team keeps one shared brain, while the engine can change as the work, provider, or budget changes.
A team does not need one generic chatbot. Keep Researcher, Finance, Designer, and other roles in the same roster, then choose the model that fits each assignment.
Channels, Notes, Boards, files, sources, and approvals stay in the Space. Change the engine without exporting the team brain or starting over somewhere else.
Use managed AI usage on paid plans or bring supported provider keys when you need direct control. Admins can decide which models and usage patterns fit the Space.
Model availability can change by plan, provider, and beta rollout. The durable role and Space context stay useful as the model underneath evolves.
Research and synthesis
Planning and analysis
Creative and multimodal work
Fast perspective and exploration
Bring your provider key
Bring your provider key
Bring your provider key
Bring your provider key
Bring your provider key
Connect a custom agent
It means a Space can work with AI from more than one provider. Your team can choose the model that fits a role or task instead of rebuilding the workflow around one lab.
No. Arc 30 is designed around durable roles. The Researcher can use one model, Finance another, and the team can change the engine without losing the role, history, or Space context.
No. Provider and model availability can depend on the plan, connected keys, provider availability, and beta rollout. The roster is a guide to the model layer, not a promise that every model is always available.
Your team context, notes, roles, and work history stay in Lydo. You can change the model underneath a teammate without moving the whole workspace to another provider.