Leap allows for alternate service URLs on a per-tenant and per-site basis. This can be very helpful when we must obfuscate a URL or change the name for product branding.

Leap lifecycle routes define the general path of a leap request. Understanding the leap lifecycle is critical to developing robust implementations.

Leap implements a common request/response queue pattern that all services share. Learn how to implement this pattern for execution routes and more.

Learn how to call services that are part of a different Feature, handle the response, and access the values from Leap Data Context

Picking the proper database for your project shouldn't be a hard decision. Learn how to choose which of the two primary DBs you should use.