Customer support
A support specialist brings ticket context and its sources into one workflow.
Lower handling time.
You know your clients and the work they need to improve. With Applet.one, turn that understanding into internal apps, hands-on enablement, and ongoing services.
The client. The process. The opportunity.
Build and run personal apps, in the cloud or in your client’s environment.
From advice to something people can use.
Available today.Applet.one is live: start from a template or prompt and publish a personal app.
Runs in your client’s environment.An on-premises version of Applet.one runs on your client’s own Kubernetes cluster.
Built on open source.Apps follow the proven Durable Objects model and run on open-source components like celld.
Most organizations already have access to AI. The harder question is what it improves. Many still use it for summaries and email drafts.
With personal apps, the people doing the work build the tools they need, right where problems occur, without a backlog. Sometimes one user is enough. The apps work alongside ERP and CRM, not instead of them. Stripe and Ibotta already run internal platforms for this.
Automate one small task at a time. Let the value compound.
Think about the work: the cumbersome tasks people face every day, the steps they repeat, and the moments when they wish they could say, “Hey computer, please fix this.”
A support specialist brings ticket context and its sources into one workflow.
Lower handling time.
An analyst lets colleagues explore business questions while keeping the calculations consistent.
Answers without a new report each time.
A finance team member compares invoices with purchase orders and flags only the mismatches.
Less checking, fewer overlooked errors.
Each app runs in its own isolated environment, with its logic and persistent state kept together. Fewer moving parts for users to understand, IT to oversee, and AI coding agents to manage.
Try Applet.oneStart from a template or prompt and build a personal app for a recurring task. Try the approach in your own work, or with a client.
The same app model on your client’s own Kubernetes cluster, keeping the infrastructure and data under their control.
Organization-wide building and sharing, with centrally managed data connections, permission-aware access, and administrative controls.
Employees build and share useful tools while the organization keeps control over data access and operations. We are developing the enterprise version with a small group of design partners, and you and your clients can help shape it.

Centrally managed data connections. Access follows each user’s existing permissions, so sharing an app never shares data.
Which apps exist, who owns and uses them, and what data they touch, with controls to intervene where needed.
Apps linked to an intended outcome or KPI, so adoption is measured by improvements in work, not tokens used.
An app is only part of the engagement. Real use reveals what the solution should be, and your expertise turns that into the next step.
Find a recurring task, build a focused app, and test it in real work.
Turn a business process into a tool people use, then refine it with their feedback.
Help client teams build apps themselves, with training, shared context, and clear boundaries.
One app can reveal improvements nobody planned. Work with its builder to rethink the process and spread it across the organization.
Tell us about your work, the clients you support, and a workflow you would like to improve. Together, we can explore what a first engagement could look like.