Trillo Workbench is an application platform that sits in your cloud environment. It enables you to build cloud applications in one-third of the time and at a fraction of the cost of traditional development.
Conventional applications require backend application engineers to work hand in hand with cloud architects and DevOps engineers. They need to develop a core platform for database, storage, security, and other common services. They are also responsible for non-functional requirements such as security (authentication and authorization), performance, and reliability engineering.
Trillo Workbench frees application engineers from the burden of developing core service, DevOps, and non-functional requirements. Think of Trillo Workbench as a middle layer that sits between an application and cloud. Workbench provides 80% of the core services needed to write an application. You write the remaining 20% – application service code that includes schemas and logic. Workbench configures and manages the backend cloud infrastructure for you.
Most applications need access to databases, file management, user authentication, and more. Trillo Workbench provides these common services out of the box. It acts as an intermediary between your code and the backend cloud infrastructure.
Building an application starts with the Trillo Workbench UI. Database schemas are created, user roles and access are configured, storage buckets are defined, etc.
Using your favorite IDE (or the built-in code editor in Workbench), you create your application logic using Java or Python (other languages will be added soon). Your application code becomes serverless functions in Workbench. You will also create workflows, scheduled jobs and tasks, and other logic for your application.
Trillo Workbench will create APIs from these functions. Access to databases and file management, logs, and more is provided by Workbench APIs. You simply write your code to use these APIs and Trillo Workbench manages all the infrastructure on the backend for you. All of the cloud infrastructure is abstracted away and you don't need to worry about it (or need the help of a DevOps team to build or manage it).
Trillo Workbench runs as microservices on a Kubernetes (GKE) cluster in your hyperscaler environment. Because it's scalable, it can handle applications of almost any size and is designed for heavy enterprise-level production workloads.
Workbench interfaces with Cloud services (on behalf of your application) using recommended best practices for security and performance.

Using the above diagram, the process of building an application with and without Trillo Workbench is described below. It refers to 'A' (application), 'P' (platform), 'C' (cloud) from the above diagram.
The closest platform to Trillo Workbench is Microsoft Power Apps. Other similar products in the space are Salesforce, Outsystems, Appian, Mendix, and Zoho.
Trillo Workbench offers distinct advantages over its competitors in the following ways.
Services provided by Trillo Workbench include:
Features provided by Trillo Workbench low code development platform include:
Note that this is not an exhaustive list of services or features. Additional features are described in the documentation.
The basic building blocks required for a Workbench application include:
Workbench is a Cloud-Based Application Development tool, extremely scalable and designed for complex, enterprise-level application development. In general, Workbench has very few limitations. However, there are a few application types that are not a good fit for Workbench. Examples of these would include AI/ML model training and streaming big data pipelines (there are specific cloud-native services that work better for these application needs).
Trillo Workbench has been available for nearly 6 years and is running applications in production environments for numerous companies.
Trillo Workbench can be deployed in a GCP or Azure environment (and soon in AWS). Refer to the following document for additional information.
Trillo Workbench Installation Document
Once Trillo Workbench is deployed, you will receive a unique URL to the Workbench console, as well as a user ID and password. You can then log in to the console and invite other users to collaborate on your project.