VPServBeta
VPServ Beta

A guided Android workspace with advanced control when you need it.

VPServ combines a visual application interface, an advanced local terminal, and a private developer runtime for practical project work on Android.

  • Install supported tools through the application interface.
  • Open projects and tap Run Environment for prepared workflows.
  • Use the terminal only when advanced control is useful.
Read DocumentationDownload VPServ

One private runtime

Choose the interface that fits the work.

Android

Visual Tools Manager

Supported catalog and managed installation

Guided

Projects + Run Environment

Prepared project workflows in the app

Visual

Advanced local terminal

Optional custom commands and debugging

Optional
Projects, installed tools, commands, and output stay within the same VPServ-managed environment.

Guided application workflow

More than a terminal: a visual workflow for prepared projects.

VPServ gives people an Android interface for supported tools, saved projects, and prepared project execution—without requiring them to manually enter every command.

VPServ application

Global Tools Manager

Guided UI

Selected supported tool

Manifest retrieved from VPServ

Select

Choose a supported tool to begin

Installation progress and logs stay visible in the application.

Prepared project
Abotlogixfile.json

Project action

Run Environment

Ready · Supported tool catalog retrieved from VPServ

An illustrative guided flow: discover a supported tool, install it through the application, open a prepared project, and start its configured workflow.

Beta

Global Tools Manager

A visual supported-tool catalog that keeps installation inside VPServ rather than asking users to manage package archives themselves.

  • Retrieves the supported tool catalog from the VPServ server.
  • Shows tool names, available versions, local installation state, and supported daemon state where available.
  • Lets users tap Install for a supported tool.
  • Shows installation progress and logs while VPServ handles the selected manifest and internally managed dependencies.
  • Lets supported daemon tools be started or stopped from the application UI.
Beta

Visual project interface

Add, view, and open saved projects through the Android application before deciding whether the terminal is needed at all.

  • Add a project and return to saved projects later.
  • Open project details and view the configured environment.
  • Browse the selected project's files and folders.
  • Use a trusted prepared project without requiring terminal knowledge for every step.
Beta

Run Environment

Start a prepared project workflow from the application interface with the project recipe as the source of configuration.

  • Reads Abotlogixfile.json from the selected project root when it is present.
  • Prepares missing supported tools identified by configured services.
  • Runs optional setup commands, starts configured services, and applies configured delays.
  • Uses supported MariaDB SQL initialization and an optional configured tunnel when the recipe asks for them.
  • Makes available execution output and logs visible for the Beta workflow.

Abotlogixfile.json

Project root recipe

Beta
project_nameproject identity
app_urloptional local URL
setup_commandsoptional preparation
servicesruntime processes
tunneloptional named tunnel
A trusted project recipe can be prepared once, then run through VPServ's application interface by another trusted user.

Project automation

Make a project workflow repeatable, not mysterious.

Beta

Abotlogixfile.json is a declarative VPServ project recipe placed in the project root. It lets a project author define the pieces a prepared workflow needs so trusted collaborators can repeat it through the application interface.

  • Project identity and an optional application URL
  • Optional setup commands
  • Runtime services and their command arguments
  • Configured service startup delays
  • Supported MariaDB SQL initialization scripts
  • Optional named Cloudflare tunnel configuration

When Run Environment is tapped, VPServ can read the recipe, prepare identified supported tools, run optional setup commands, process services in order, apply configured delays, run supported SQL initialization, and start an optional configured tunnel.

Explore Abotlogixfile.jsonView examples

Managed package system

Beta

Supported tools, managed as part of VPServ.

VPServ uses a server-provided tool catalog, tool manifests, and dependency-aware installation inside its private runtime. The Visual Tools Manager is the guided path; the terminal is available for advanced users.

vpkg and pkg

Use vpkg for VPServ package workflows. For advanced terminal work, pkg is available as a convenient linked command for supported tools.

Read about managed tools

A managed installation path

From a supported tool choice to visible progress and logs.

  1. 01

    Supported catalog

    VPServ gets supported tool choices and their versions from its server.

  2. 02

    Tool manifest

    The selected supported tool is resolved through its server-provided manifest.

  3. 03

    Managed dependencies

    The VPServ package engine handles required dependencies inside the private runtime.

  4. 04

    Visible progress

    The application surfaces installation progress and logs as the managed workflow runs.

VPServ does not present this as arbitrary package installation or full Debian compatibility. The focus is a managed workflow for supported tools and their internally handled dependencies.

Use VPServ your way

A visual path first. An advanced terminal when it helps.

Both paths use the same private VPServ runtime. Choose the guided application flow for prepared work, or move to the terminal when a project needs manual control.

Beta

Guided interface

Prepared projects and one-tap workflows.

  • Best for trusted prepared projects and one-tap workflows.
  • Use Global Tools Manager, projects, Run Environment, and visible logs.
  • No terminal knowledge is required to run every prepared step.
Global ToolsProjectRun Environment
Beta

Advanced terminal

Custom control when you need it.

  • Best for custom commands, debugging, and manual control.
  • Use installed VPServ tools plus pkg or vpkg workflows.
  • Inspect direct command output in VPServ's local terminal.

vpserv $ pkg install <supported-tool>

vpserv $ run custom-command

The primary terminal workflow is local to VPServ; it does not require a remote SSH session.

Supported development workflows

Choose a familiar runtime. Keep the VPServ workflow consistent.

Use prepared projects for common Python, PHP, Node.js, and MariaDB workflows. Availability labels make the current level of compatibility clear before you start.

Beta

Current workflow

Python and pip

Use Python 3.13 workflows, pip-based project dependency installation, and prepared setup commands when a project needs them.

  • Run Python scripts in the VPServ runtime.
  • Install a project's requirements through a prepared setup command.
  • Start a supported Python web workflow such as Flask when the project is prepared for it.
Beta

Current workflow

PHP

Run PHP development-server workflows, serve a project folder locally, and use PHP as a configured project service.

  • Use a local PHP development-server workflow.
  • Serve the selected project folder as a local project service.
  • Define PHP as a service in Abotlogixfile.json for a repeatable workflow.
Experimental

Compatibility workflow

Node.js and npm

Run supported Node.js project commands, npm workflows, and prepared setup or service commands with compatibility treated carefully.

  • Install project dependencies and run supported Node.js project commands.
  • Use npm from a project setup or service workflow when it has been tested in VPServ.
  • Native modules and package compatibility can vary; do not assume every npm workflow will work.
Experimental

Compatibility workflow

MariaDB and daemon workflows

Use the current MariaDB startup and SQL initialization path, with database and multi-service behavior clearly marked as experimental.

  • Initialize MariaDB on first run when the workflow needs it.
  • Run existing project-root SQL files through the supported MariaDB initialization path.
  • Reuse a detected globally running supported daemon process when available.

Workflow availability reflects the current VPServ Beta experience. Experimental labels are intentional: compatibility can vary by device, package, project, and dependency.

Command and service execution

From a prepared action to visible execution.

VPServ separates preparation from long-running services so a prepared project workflow is easier to follow from the Android application or the local terminal.

Step 01

Before services

Setup commands

Use optional setup commands for preparation, dependency installation, project files, or a supported build step. VPServ processes them synchronously in listed order before services.

Step 02

Listed order

Runtime services

Use services for long-running application or database processes. VPServ processes configured services in listed order as part of the foreground-managed project workflow.

Foreground-managed project execution

Run Environment starts the prepared project workflow from the Android application.

Beta

Local hosting and private runtime

Keep development local. Share intentionally.

VPServ is designed around a private Android application runtime: a practical place to run supported local services, inspect their output, and optionally expose a configured service when a project truly needs it.

Beta

Supported local services

Develop locally, then use a configured tunnel only when it belongs in the workflow.

A project can start a supported local web service and use its configured URL. When a trusted recipe includes a named Cloudflare tunnel, VPServ can prepare the required supported tool and start the configured tunnel as part of that workflow.

  • Run a supported local web service from a prepared project workflow.
  • Open a configured local application URL when the project provides one.
  • Use an optional configured Cloudflare named tunnel when intentional remote access is needed.
  • Let VPServ prepare the supported Cloudflare tool when a project recipe requires it.

Tunnel tokens are secrets. Keep them out of public repositories, rotate exposed tokens, and expose services only when you intend to make them reachable.

Beta

Private Android runtime

One VPServ environment across the interface and terminal.

VPServ maintains its own application runtime for supported installed tools and project execution. It keeps guided and advanced paths connected without asking a project user to reproduce every environment step manually.

  • Installed tools and project execution remain managed by VPServ.
  • Guided application and advanced terminal workflows use the same VPServ runtime.
  • Prepared projects can use supported path placeholders where the recipe supports them.

This is a managed development environment, not a production cloud-hosting service or a substitute for a dedicated production deployment environment.

Feature status

Clear about what is ready to try and what is still evolving.

VPServ is a Beta product. This view distinguishes current workflows from compatibility-sensitive experiments and longer-term product direction.

Beta

Available in Beta

Current workflows people can try today, with Beta expectations kept visible.

  • Global Tools Manager and managed supported-tool installation
  • Visual project management and Run Environment
  • Abotlogixfile.json project recipes
  • Local terminal, command execution, and logs
  • Python and pip workflows
  • PHP local service workflows
  • Configured Cloudflare tunnel workflows
Experimental

Experimental workflows

Useful areas under active validation where device or package behavior can vary.

  • Node.js and npm compatibility, especially native or device-sensitive dependencies
  • MariaDB, database initialization, and multi-service project workflows
  • Device-dependent package compatibility and daemon behavior
Planned

Planned

Roadmap-level improvements VPServ is working toward, not availability promises.

  • Broader supported-tool catalog coverage
  • Improved runtime state and project stop management
  • Expanded database workflows and improved project automation
  • Defensive security tools, authorized local security labs, and developer security education

Roadmap context

Planned items are not presented as current product availability.

Explore the roadmap for the broader direction behind these summaries.

Explore the roadmap

Ways to use VPServ

Start with a prepared flow, then take control as needed.

VPServ can meet a project where it is: a trusted one-tap workflow for a teammate, or a local terminal for the developer who needs to inspect and adjust every command.

Beta

Prepared web project

  1. 1Open a trusted prepared project.
  2. 2Tap Run Environment.
  3. 3VPServ prepares the identified supported tool and runs optional setup commands.
  4. 4The web service starts and VPServ can present the configured local URL.
The guided path remains visible from project setup through local application access.
Experimental

PHP and database project

  1. 1Start the configured MariaDB service.
  2. 2Apply supported existing SQL initialization files.
  3. 3Start the PHP service and open the local application.
  4. 4Optionally start a configured named tunnel when the project intentionally needs one.
Beta

Advanced developer workflow

  1. 1Open the local terminal.
  2. 2Use pkg or vpkg for a supported tool workflow.
  3. 3Run custom project commands and inspect output.
  4. 4Turn a tested repeatable flow into Abotlogixfile.json.
Beta

Guided user workflow

  1. 1Receive a trusted prepared project.
  2. 2Add it to VPServ and install a requested supported tool through the UI.
  3. 3Tap Run Environment and follow the visible output.
  4. 4Open the configured application when VPServ presents it.

Beta, with clear boundaries

Build confidently by knowing what to expect.

VPServ is designed for practical Android development workflows, but it is still a Beta product. These limits help set accurate expectations before a project is shared or run.

  • VPServ is in Beta, so behavior and availability can change.
  • Android device differences can affect package and workflow compatibility.
  • Not every Linux package, npm dependency, or Python dependency is guaranteed to work.
  • Some daemon, database, and multi-service workflows remain experimental.
  • Prepared project recipes can install supported tools and execute commands, so they must come from trusted sources.
  • Do not rely on a Beta build for critical production workloads.

VPServ Beta

Bring a trusted project workflow to your Android development environment.

Start with the guided interface, inspect the details in the terminal when needed, and keep repeatable project workflows documented in Abotlogixfile.json.

Download VPServRead DocumentationExplore Abotlogixfile.json