meshployapps

Your app drive.

Drop in an app and it is online at its own address. Share it the way you share a doc. Everyone you share it with opens it from a link.

apps.acme.meshploy.cloud
lead-desk/
lead-deskBuilding
lead-desk.acme.app
PAv1 · now
expense-trackerRunning
expenses.acme.app
PRK v7 · 2h ago
quiz-nightStopped
quiz.acme.app
Anyone with the link v3 · Tue
notesRunning
notes.acme.app
P v12 · Oct 28
rotaRunning
rota.acme.app
PA v4 · Oct 30
Drop a folder to put it online
Shared with Asha · she gets a link by email

Made with AI.
Online in one step.

Claude Code, Lovable, Bolt, Cursor or your own hands: whatever made it, a folder is all Meshploy needs. It leaves out what should not leave your computer, such as .env files and installed packages, builds the rest and gives it an address.

  • Its own address, with HTTPS
  • Built for you; no Dockerfile needed
  • A new version each time you drop it in

Share it like a doc.

Type an email address. They get a link, sign in with their email and the app opens. Take access away just as easily; it stops working for them at once.

What Asha sees.

Only the apps shared with her, as tiles. No console, no settings, nothing to learn. She signs in with the email you shared with, and opens them.

Everything a small app needs.

And nothing you have to look after yourself.

Versions

Every upload is kept. Go back to the last one that worked in one click.

Your own domain

Answer at tools.yourcompany.com as well as at its Meshploy address, HTTPS included.

Private or public

Invite-only by default. Open it to anyone with the link when you want to.

A database when it needs one

Postgres, MySQL, Redis or MongoDB next to your app, with its address handed to it.

Settings without code

Keys and settings your app reads, kept out of the folder and out of sight.

Logs when it misbehaves

See what your app printed, restart it, or ask your agent to look.

Already working with an AI agent?

Connect it once. Claude Code, Cursor, Codex and any assistant that speaks MCP can put your app online, share it and read its logs, with only the access you give it.

How agents connect
you › put ./lead-desk online and share it with asha@acme.com
agent › packing lead-desk/ (14 files, 41 KB)
› building… done in 52s
› live at https://lead-desk.acme.app
› shared with asha@acme.com; she has a link in her inbox

you › it is showing an error on the form
agent › the logs say SMTP_HOST is not set. Want me to add it?

When it grows, it stays put.

The drive is one face of a full Meshploy workspace. Open any app in the console and it gains staging, your own machines, scheduled jobs and backups, at the same address.

meshployworkspace

Free to start.

Put your first apps online and share them at no cost. Paid plans add more apps, more people and more room, when you need them.

See pricing

The questions worth asking.

What can I put online?

A folder with a web app in it: Node, Python, Go, PHP, Ruby, a static site, or anything with a Dockerfile. Meshploy works out how to build it.

Do the people I share with need an account?

They get a link by email and sign in with that email address. There is no password to make up and nothing to install.

Can I make an app public?

Yes. An app can be invite-only, or open to anyone who has the link. You can change it at any time.

What happens to my data when I change an app?

Each upload is a new version. The app's database and files stay as they are, and you can go back to an earlier version in one click.

Can I use my own domain?

Yes. Point it at Meshploy and the app answers there with HTTPS, as well as at its Meshploy address.

What if my app outgrows this?

Open it in the full console: the same app gains staging, your own machines, scheduled jobs and backups. Nothing has to move.

Put your first app online today.

Free to start. Your own machines whenever you want them.