Starter
free
- Calendar, mail, operatives, and routines
- 1 GB Disk storage
- Vector: 30 requests/hour, then 12/hour
- 1 operative
- 2 routines
- No channels
For trying IOSYA with one operative, a single calendar and mailbox, and starter request limits
Save time by automating your daily tasks with Routines
Put your Operatives on a schedule and get proactive results faster.
From repeated briefing to reusable context
Routines turn one-off instructions into durable patterns your operatives can run on a schedule — with sources, outputs, and history attached.
Stop rewriting the same brief
Recurring work should not restart with a blank prompt. A routine keeps the brief, approved sources, and tone in one pattern.
TriggerBriefSourcesOutputStandardise recurring responses
Onboarding replies, handoffs, and stakeholder updates share one operational language — edits and corrections carry forward.
TemplateReviewSendHeritagePrep and follow-up in one loop
Meeting prep, session notes, and next actions stay inside the project instead of scattered documents.
ContextExecuteCaptureFollow-upEvidence that survives the session
What was requested, produced, and corrected remains inspectable when the routine runs again.
RequestWorkEvidenceReuse
Extend your work surface
Work happens in messengers, email, and the tools you already use. Connect channels and tool slots so operatives can act without breaking your flow.
Messengers
Operatives meet your team where conversations already run.
SlackTeams
WhatsAppTelegramEmail
Inbox threads, follow-ups, and drafts stay tied to the operative.
EmailWorkspace
Files, calendars, and apps your team already relies on.
Notion
Google Drive
Files
Calendars
Web
Trusted by
Pricing
Signal
€20
- Calendar, mail, operatives, routines, channels
- 15 GB Disk storage
- Vector: 300 requests/hour, then 60/hour
- 4 operatives
- 80 routines, 2 channels
For small teams that need channels, more operatives, and higher routine capacity
Station
€200
- Calendar, mail, operatives, routines, channels
- 300 GB Disk storage
- Vector: 900 requests/hour, then 180/hour
- 20 operatives
- 400 routines, 10 channels
For teams that need broader capacity across mail, channels, operatives, routines, and Disk
Enterprise
custom
- Custom features
- Custom storage capacity
- Custom request limits
- Custom operatives
- Custom routines and channels
For organizations that need a tailored deployment, limits, and support
Explore success stories
Questions
What's a request?
A request is the unit of model work capacity shown on your plan. Plans scale by hourly request limits — we say requests, not credits.
Where does memory live?
Memory lives with the operative inside your workspace — sources, routines, and session history carry forward instead of resetting each chat.
Can I audit a decision?
Work in IOSYA is designed to be auditable: actions, sources, and context stay tied to the operative and project they belong to.
How is this not another chat wrapper?
IOSYA is built around permanent operatives and continuing sessions, not disposable chats that forget what happened yesterday.
Keep your project knowledge working
With operatives remembering your actions and outcomes, your results stay with you — no more starting from zero.