🔌
MCP server
Claude, ChatGPT or your own agent talk to your data via MCP — with the same rights and the same confirmation as Bob.
Developer Studio
For when you do want code — without leaving the platform.
Functions run in a sandbox with access to your apps, entries and actions — as a workflow step, via API or on Bob's request. Websites are hosted, with forms and shop widgets. Everything becomes a package you take to other organisations.
- Python & JavaScript in the sandbox
- Hosted websites
- .yasapp / .yasfn packages
- REST API & webhooks
- MCP server
Functions
One call, three callers.
A function is an action like any other: the workflow calls it as a node, the API calls it via HTTP, Bob calls it on request — and all three go through the same door with the same rights. Runs are logged with input, output and error, and can be resumed.
Packages & App Store
Built once, used everywhere.
An app with fields, statuses, roles, actions and templates becomes a .yasapp file, a function with its versions a .yasfn — both travel to another organisation without anyone rebuilding anything. In the Store you find ready-made industry solutions from us: reviewed, versioned and provided by us.
Dashboards & custom views
Your own views — as widget, as HTML, as page.
Dashboards with widgets per role, shareable with the team. Custom HTML views render your data in your markup — sandboxed, with data queries Bob can write too. And whoever needs a whole page hosts it in the Studio.
📦
Packages
An app with fields, statuses, roles and templates as .yasapp; a function with versions as .yasfn. Take it between organisations; ready-made solutions from us are in the Store.
🛡️
Sandbox, not server
Code runs isolated with time and memory limits, sees only what the calling user may see, and has no path into other organisations.
Ready to free your processes from tool chaos?
No-obligation introductory call. We build a live app with you that mirrors your real workflow.