Wrkr is preparing for invitation access. Paid checkout is not open. These guides describe the planned service; example requests are starting points you can adapt. See pricing and availability.
Use the tools your job needs
Your selected AI can use the terminal to install compatible software and libraries in your Linux workspace. Python can process data, FFmpeg can work with media, and Node.js and Git can support app development. Your computer’s capacity and software compatibility govern what runs.
You control your Linux environment, not Wrkr’s host infrastructure, kernel or account quotas. An installed tool still needs correct setup, valid licenses where relevant and a result you can review.
Connect accounts through your AI tool
Workers can use connections supported by the selected AI tool. A workflow might read a Google Drive brief, prepare a Gmail draft and organize next steps in Google Sheets. The website’s tool directory illustrates possibilities; it is not a verified inventory of first-party Wrkr integrations.
Availability depends on the AI tool, permissions, account, operating environment and any required local software. Connecting a paid service does not include its subscription or API allowance. See AI accounts and billing.
Plugins, skills and MCP
- Plugin
- A bundle of tools and instructions supported by the chosen AI tool.
- Skill
- A reusable method and supporting resources that guide the AI through a type of work.
- MCP server
- A connection that exposes additional tools or data to a compatible AI tool. It requires its own setup and permissions.
For example, a video skill can guide the AI to set up a project, write a composition and render it. The skill does not itself supply a paid media-generation account or guarantee a finished result.
What small-app hosting includes
Each worker has one HTTPS app link under apps.wrkr.dev. The launch offer is for small apps and demos shared with a friend or client. The app and computer must stay running; workers and apps share the account’s resources.
- App link
- One Wrkr HTTPS address per worker. Domain registration and custom domains are not included.
- Database
- SQLite on the computer’s disk. The AI maintains the data model.
- Sign-in
- The AI builds the app’s customer sign-in using an established library and local data. Wrkr’s own sign-in protects your computer, not your app’s visitors.
- Files
- Local disk storage within account capacity and the published backup scope.
- Scheduled jobs
- The worker’s scheduler, requiring running compute, valid access and available resources.
- Cache
- App memory or local files, with refreshing and persistence managed by the app.
Which costs are separate?
These local app capabilities need no separate hosting, database or basic scheduler subscription. External services use your own accounts and separate billing: AI access, paid media generation, app email, connected-service plans, software licenses, data APIs, message delivery and payment processing.
Email verification, magic links and password-reset messages require an outside email provider. Customer-facing AI also requires separately funded AI access. The Wrkr subscription does not cap outside bills. Read the plan and outside costs.
Review before sharing
Test the app’s permissions, customer sign-in, data handling and error states. Keep a copy of important work and understand backup and recovery limits. Your AI builds and maintains the app; included computer capacity is not a promise of high-traffic hosting.