Templates are a special kind of JSON-based files that defines a structure and base files for a new lambdas/functions/apps.

Templates could be embedded and external. External templates folder by-default should be located in a working directory as .templates and could be changed by --templates flag of TEMPLATES environment.

Name file will be a name of template (except .json).

Templates could define files, manifest, actions to invoke after clone and required checks.

Minimal working template file:

  "manifest": {
    "run": ["echo", "hello world"]


  • description (optional, string): short description of template
  • manifest (required, Manifest): manifest definition for a new lambda
  • post_clone (optional, string): action to invoke after clone
  • checks (optional, array of array of string): list of commands to invoke to check template availability (see example below)
  • files (optional, map of string to string): files and content in a new lambda

If at least one check failed - template will be disabled.

Example check to ensure that template will be available only if python3 and pip3 installed:

  "checks": [
    ["which", "python3"],
    ["which", "pip3"]


Most embeddable templates will be available in Docker image or via installing debian package (with recommended packages - installed automatically by default)

List of embedded templates below:

Table of contents