Skip to content
Proyectos

botpress/nlu has 26 GitHub stars and 24 forks. GitHot measured 0 stars in 24 hours and 0 in 7 days. Last checked 2026-11-21 08:40 UTC. Last push 2026-06-22.

Cómo se miden estas cifras

Crecimiento de estrellas medido

in 24h
0
in 7 days
0
in 15 days
Recopilando historial
in 1 month
Recopilando historial

Cambios netos en períodos que se solapan, no totales diarios. Los datos no disponibles se dejan en blanco. Las estrellas indican interés, no calidad.

Acerca de

This repo contains every ML/NLU related code written by Botpress in the NodeJS environment. This includes the Botpress Standalone NLU Server.

Herramientas de desarrollo

README.md

Original

Botpress NLU

Description

This repo contains every ML/NLU related code written by Botpress in the NodeJS environment.

The source code is structured in a mono-repo fashion using yarn workspaces. The ./packages directory contains all available packages. The main packages are:

  • nlu-server: Contains the Botpress Standalone NLU Server
  • lang-server: Contains the Botpress Language Server
  • nlu-bin: Small CLI to use as an entry point for both nlu-server and lang-server

Check out each individual packages for more details.

Running from source

Prerequisites: Node 16.13 (you can use nvm) and Yarn.

  1. Run yarn to fetch node packages.
  2. Run yarn build && yarn start to build and start the Standalone NLU server.
  3. You can also run yarn dev to run the NLU Server with ts-node however, trainings won't be parallelized on several threads.

Running from pre-built binaries

New executable binary files are packaged at every release. You can download those directly on release page located here.

Telemetry

Metrics (Prometheus)

A Prometheus endpoint can be configured to expose NLU specific metrics. By setting the PROMETHEUS_ENABLED environment variables to true, the port 9090 will expose prometheus metrics.

Tracing (Jaeger)

A Jaeger client can be configured using a subset of the standard Opentelemetry environment variables.

The important environment variables for configuring tracing are:

  • TRACING_ENABLED bool Enables the tracer
  • TRACING_DEBUG bool Adds debug information about the tracing configuration
  • OTEL_EXPORTER_JAEGER_ENDPOINT url Sets the Jaeger collector endpoint
  • OTEL_SERVICE_NAME string Sets the service name given to a trace
  • OTEL_SERVICE_VERSION string Sets the current running version of the service
  • OTEL_SERVICE_VERSION_INSTANCE_ID string Sets the node intance id on which the service is running on
  • OTEL_SERVICE_NAMESPACE string Sets the namespace of the service
  • OTEL_DEPLOYMENT_ENVIRONMENT string Sets the environment of the service

⚠️⚠️ Disclaimer ⚠️⚠️

The NLU Server does not enforce authentication in any way. This means it is completely exposed to many attacks. If you plan on using the nlu-server in your local Botpress setup, makes sure it is not publicly exposed. If you plan on exposing the NLU server, make sure it his hidden behind a reverse proxy which ensures a proper authentication. This reverse proxy should:

  • Ensure each appId (X-App-Id header) is unique.
  • Ensure a user with appId user1 can't call the nlu server with header X-App-Id set to anything other than user1.
  • Ensure only calls with a registered appId can call the nlu server except maybe for the GET /info route.

The NLU Server's only purpose is to do NLU.

Licensing

Different licences may apply to differents packages of the ./packages directory. If no licence is specified, the package is protected by the same license as the v12 Botpress repository.