---
title: Running code in Tines
url: https://www.tines.com/docs/actions/running-code-in-tines/
updated: 2026-05-21T11:27:27+00:00
---

*[tines.com](https://www.tines.com/llms.txt) › [Docs](https://www.tines.com/llms.txt) › [Actions](https://www.tines.com/llm/docs/actions.md)*

# Running code in Tines

*[View on tines.com](https://www.tines.com/docs/actions/running-code-in-tines/)*

While you can build nearly anything using Tines actions, you may find yourself wanting to solve a specific problem using code. Tines supports multiple ways of doing this, depending on your specific requirements end environment.

This is an overview of the different options:

| Feature | AWS Lambda | tines-command-runner | command-over-http |
| --- | --- | --- | --- |
| Documentation | [Cloud Run Script Action Documentation](https://www.tines.com/docs/actions/tools/run-script/) | [tines-command-runner documentation for docker compose](https://www.tines.com/docs/self-hosted/deploying-tines/docker-compose/run-script-setup/) [tines-command-runner documentation for AWS Fargate](https://www.tines.com/docs/self-hosted/deploying-tines/aws-fargate/run-script-setup/)  
  
[Run-Script-over-Tunnel documentation](https://www.tines.com/docs/admin/tunnel/run-script-over-tunnel/) | [command-over-http documentation](https://www.tines.com/docs/admin/command-over-http/) |
| Primary use case(s) | \- Zero-config Python running  
  
 | \- Self-hosted tenants  
\- Cloud customers who need to network with private resources  
\- Avoiding limitations of Cloud Run Script | \- Legacy use  
\- Using non-standard binaries  
\- Running Bash or PowerShell |
| Installation requirements | None | Customer needs to run the tines-command-runner container in their network, see requirements. | Customer needs to run the command-over-http container in their network. See requirements. |
| Cloud support | Yes, natively used via Run Script Action | Yes, via Run-Script-over-Tunnel | Yes, via Tunnel on an HTTP Request Action |
| Self-hosted Support | No, only via [story library](https://www.tines.com/library/stories/1182841/?name=create-update-and-run-aws-lambda-functions&redirected-from=%2Flibrary%2Fstories%2F). | Yes, as a sidecar container. | Yes, as a sidecar container. |
| Runtime Support | Python (version 3.13 and [custom runtimes](https://www.tines.com/docs/actions/tools/run-script/custom-runtimes/)), AWS CLI | Python (version configurable), Bash | Python 3, Bash, PowerShell 7 |
| Dependencies | Public PyPi packages | Public or Private PyPi Packages via PIP\_INDEX\_URL | Fixed. Customers can extend and run their own Docker image |
| Max timeout | 110 seconds | Default 60 seconds. Configurable via RUN\_SCRIPT\_MAX\_TIMEOUT | Default 300 seconds. Configurable via EXECUTION\_TIMEOUT |
| Maximum input payload | 6MB | No limit, depends on infrastructure | No limit, depends on infrastructure |
| Maximum output payload | 20MB | Maximum event size, depends on infrastructure | Maximum event size, depends on infrastructure |
| Networking | Public internet connectivity, floating IP address | Customer’s networking | Customer’s networking |
| Underlying resources | 1 GB Memory, 0.5 vCPU, 756GB Ephemeral storage. | Customer’s settings, bound by container configuration | Customer’s settings, bound by container configuration |