Frequently Asked Questions

WorkApps is a platform for publishing internal tools for your team. Upload a ZIP file and your team gets a secure, authenticated link instantly — no servers, no IT tickets, no deployment pipeline.

No. If you can build or export a ZIP file, you can publish it. There is no server setup or hosting configuration required.

Visit workapps.tech and click to get started. You can sign up with your email or through your organization's single sign-on provider.

You pay per published app — $59/mo for Utility apps and $119/mo for Workflow apps. There are no seat fees, so your whole team can use every app at no extra cost. Your organization also gets a WorkApps-managed subdomain ({orgSlug}.workapps.tech) included on all plans.

No. WorkApps runs entirely in your browser. There is nothing to download, install, or configure on your machine.

Two types: Utility apps (stateless tools like calculators, estimators, and generators) and Workflow apps (operational tools that store records over time, like trackers, approval flows, and internal CRMs).

HTML, CSS, JavaScript, JSON, images (PNG, JPG, SVG, GIF, WebP), fonts, and any other static assets your app needs. The ZIP must contain at least one index.html file.

Yes. On Core tier, ZIP uploads are capped at 25 MB compressed (75 MB uncompressed). Enterprise tier allows up to 75 MB compressed (200 MB uncompressed). These limits comfortably support most internal tools, including SPAs with charts and images.

Yes, as long as the app is built and exported as static files. Run your build step, ZIP the output, and publish. If it runs in a browser, it works on WorkApps.

Most apps are live within seconds of uploading. Your team can start using it immediately.

Yes. There's no cap — you pay per app, so publish as many as your team needs.

Yes. Upload a new version at any time. Your link stays the same.

You can instantly roll back to a previous version. Every published version is saved, so you can always revert.

No. When you update an app, the URL stays exactly the same. Anyone with the link will automatically see the latest version.

Core tier retains up to 25 versions per app. Enterprise and Compliance tiers retain up to 100. When the limit is reached, the oldest version is removed — but version metadata (number, timestamp, publisher) is always kept.

Yes. You can preview your updated app before making it live. Verify everything works before your team sees the change.

Yes. Multiple team members can sign in and publish, update, and manage apps from a shared dashboard — there are no per-seat limits.

Yes. All published apps are organized in a searchable dashboard. Any team member can find and access them instantly.

Role-based access control is coming soon. Enterprise posture adds organizational access controls and SSO so you can manage who can view or manage each app.

By default, apps are only accessible to authenticated members of your team. Enterprise posture adds additional controls for restricting or sharing access.

No. WorkApps is designed for internal use. Apps are not listed in any public marketplace and require authentication to access.

Yes. All data is encrypted in transit using TLS and at rest using industry-standard encryption.

Yes, with Enterprise posture. We support SAML-based single sign-on, including Microsoft Entra ID, so your team can authenticate with their existing corporate credentials.

Yes, with Enterprise posture. Audit logs track who published, updated, or rolled back apps, giving your organization full visibility into activity.

WorkApps runs on globally distributed cloud infrastructure. Your apps are served from edge locations close to your team for fast load times.

Yes. You can delete individual apps or your entire account at any time.

Every organization gets a WorkApps-managed subdomain at {orgSlug}.workapps.tech. Your apps are available at {orgSlug}.workapps.tech/{appSlug} — no configuration required.

Yes, with Enterprise posture. You can connect one customer-owned subdomain (e.g. tools.acme.com) to your organization. All your apps are then available under that hostname. Apex/root domains (e.g. acme.com) are not supported in self-serve.

No. Custom hostnames are an Enterprise posture feature. All Core accounts use a WorkApps-managed subdomain ({orgSlug}.workapps.tech), which is included at no extra cost.

One per organization. A single custom hostname covers all your apps — there is no per-app domain configuration.

Your custom hostname is disabled and all traffic must route through your {orgSlug}.workapps.tech address. No traffic is cut off mid-billing cycle, and you'll see a clear warning before confirming any downgrade.

No. WorkApps works for any internal app you've built, regardless of how it was made.

Yes. If an AI tool produces HTML, CSS, and JavaScript files, you can ZIP them and publish on WorkApps. Most AI coding tools output exactly this format.

Iterate freely. Publish, test with your team, then upload an improved version. Instant rollback means there's no risk in trying.

Monthly, per published app. New apps are prorated to your billing cycle anchor date. Account posture (Enterprise or Compliance) is a flat monthly add-on that covers your whole account.

Yes. Add apps whenever you need them. Removed apps stay live until the end of the billing cycle — you won't lose access mid-month.

We accept all major credit cards. Enterprise and Compliance accounts can also be invoiced.

Contact us and we'll set you up with a trial. We'd rather talk through your use case than hand you a generic 14-day timer.