Elixir at Ramp
![]()
Pablo Meier, one of Ramp's first hires and a long-time Erlang fan, explains where Ramp uses Elixir: the real-time authorization engine, which needs very high uptime, and the risk analysis platform, which needs concurrency and data-pipeline ingestion. He credits the BEAM and OTP with the concurrency, fault tolerance and handling of transient errors he has missed elsewhere, and Elixir with friendlier syntax and tooling than plain Erlang. The trade-offs he names are a steeper adoption curve, some dislike of the syntax, and Dialyzer being weaker than mypy, TypeScript or Sorbet. Ramp's largest service is still Python, and he argues that team culture matters more than the language.
Was this useful?