# Start from the terminal. Connect with SSH, upload your app, and share a link. Linux computers for dev sandboxes, agents, and apps. Use the terminal ```sh ssh treliso.dev ``` Run this command to set up your workspace. 7 day free trial · Cancel anytime · 24/7 support ## A computer for whatever you’re building. Treliso gives your project an isolated Linux VM, SSH access, and an HTTPS address. Use it as a sandbox for your code, a workspace for an agent, or a home for an app people can open in their browser. Your Ubuntu workspace comes with Node, Python, Go, and Rust. Connect as root from your own terminal, move files with SCP or SFTP, and use the browser console to manage the VM. [Meet your workspace](https://treliso.com/docs/#your-workspace) Your isolated workspace **Your code, tools, and files** `127.0.0.1:3000` `cedar-otter.treliso.dev` Environment Ubuntu Linux Runtimes Node · Python · Go · Rust Access SSH · SCP · SFTP Web address HTTPS included Example VM name. Yours is assigned when you sign up. ## Room to experiment. A place to run. From an isolated development sandbox to an app your team uses every day. Put a Linux computer behind your next project. ### Isolated dev sandboxes Give an experiment its own Linux environment. Run code and inspect files inside the VM, keeping the work separate from your laptop and your other projects. Try it for a proof of concept, a test service, or a tricky bug reproduction. ### Computers for your agents Give a coding agent a workspace to operate in. Connect through SSH, or use hosted MCP where enabled, to work with code and files inside the guest. Try it for agent-built prototypes and tool-driven workflows. The agent uses the permissions you grant it. ### Small tools for your team Build the focused app that makes a recurring task easier. A browser link gives colleagues a way to use it without setting up a local environment. Try it for a reporting dashboard, a request tracker, or an admin tool. Add your own login for private data. ### APIs and webhook endpoints Run an HTTP service behind your VM’s HTTPS address. Test it with your own clients or connect another service to your endpoint. Try it for a small API, a webhook receiver, or an integration prototype. ### Apps you can pass around Turn a local project into something your friends or community can open. Share the URL, gather feedback, and keep improving it in your own tools. Try it for a product demo, an event page, or a community directory. ### Automation and scheduled scripts Give repeatable jobs their own workspace. Run scripts in the guest and use your own cron or CI scheduler to trigger work through the guest-control API where enabled. Try it for file processing, report generation, or recurring maintenance. Scheduling comes from your own tooling. ## From a command to a link Start with the included tools, or bring code you’ve built locally. 1. ### Connect Run ssh treliso.dev. Enter your email, approve your SSH key, and connect to your first VM. 2. ### Run your app Use the included runtimes or upload a compatible Linux executable. Have your web app listen on 127.0.0.1:3000. 3. ### Share it! Your VM gets a public HTTPS address. Send that link to the people who should open the app. your-app.treliso.dev [Follow the guide](https://treliso.com/docs/) [Open the API schema](https://console.treliso.com/api/openapi.json) ## Keep the workflow you already know. Use familiar tools like Git, tmux, curl, and your choice of runtime. For a first web app, copy a standalone Node server to your VM and start it from the shell. Your HTTPS address forwards requests to port 3000. Once your app is listening, you can open it in a browser or call it with your usual HTTP tools. [Run your first app](https://treliso.com/docs/#run-your-app) On your computer ``` scp ./server.mjs cedar-otter@treliso.dev:/root/server.mjs ssh cedar-otter@treliso.dev ``` Inside your VM ``` node /root/server.mjs ``` From another terminal ``` curl https://cedar-otter.treliso.dev/ ``` Example commands: replace `cedar-otter` with your VM name. Configure your app to listen on `127.0.0.1:3000`; this foreground process runs while your SSH session stays connected. ## Go from hands-on to automated. Use the browser console when you want to check on a VM. Use the customer HTTP API when you want to make those operations part of your own tooling. Building with an agent? The HTTP and MCP interfaces share customer operations. Hosted MCP and guest controls are available when enabled for your deployment. [Explore the API schema](https://console.treliso.com/api/openapi.json) [Read the agent guide](https://treliso.com/agents/) - ### Manage your VMs Inspect VM state, request starts and stops, and track asynchronous operations to completion. - ### Control account access Manage permissions and SSH key enrollment. API operations follow your account roles and authorization. - ### Work inside the guest Where guest control is enabled, use supported commands, file operations, and managed app controls. ## A few things to know before you build. [Read the setup details](https://treliso.com/docs/#good-to-know) ### What tools are ready to use? The developer image is Ubuntu with Node and npm, Python and uv, Go, and Rust already installed. You also get Git, GitHub CLI, tmux, curl, and standard Linux tools. You can upload your own executables and files too; match compiled binaries to your VM’s architecture. Docker and systemd aren’t installed in the current image. ### How does my app get an HTTPS address? Your VM gets an assigned name and a public address such as `cedar-otter.treliso.dev`. HTTPS requests are forwarded to your app listening on `127.0.0.1:3000`. Use the actual name shown in your welcome session. ### Can I use it for a private team tool? Yes, with authentication in your app. SSH access checks enrolled keys and account permissions, but your app’s HTTPS address is public. Add a login layer before exposing private data. ### How do I keep my app running? The first-app guide starts your executable in the foreground while your SSH session is connected. Where guest control is enabled, managed app controls can supervise applications and restart them after a crash or VM boot. Check your deployment’s availability before relying on those controls. ## Give your next build a home. Start from your terminal. Finish with a link. [Launch your first app](https://treliso.com/docs/) --- Source: https://treliso.com/developers/