Pajic

Oleta · Service operations

Booking infrastructure for your frontend.

Oleta manages service availability, resources, holds and reservations. Connect your website, app or portal to the same booking engine.

Explore the reference site See capabilities
Coordinated glass and titanium modules representing a shared service engine
Concept imagery · product interfaces shown below

The booking backend behind your service.

Model what can be booked and which resources fulfill it. Use the same rules across web, app and staff surfaces.

Offerings and resources

Define the service being booked and the people, rooms or other resources that fulfill it.

Availability

Evaluate available time and capacity with timezone-aware scheduling.

Temporary holds

Hold scarce capacity before the final booking is confirmed.

Booking lifecycle

Confirm, reschedule and cancel through explicit operational actions.

Organizations and applications

Separate tenant data and bind applications to their organization, environment, origin and scopes.

API and SDK

Use the OpenAPI contract and typed @pajic-llc/oleta-sdk rather than copying booking logic into a frontend.

Try the booking lifecycle.

Pick an example time, create a hold, then confirm or cancel it. This example runs locally and creates no real booking.

Example appointment

Choose a time to see how availability becomes a hold and then a reservation.

Available times

Available

Choose a time, then create a hold.

Interactive example · no reservation is created

Use explicit booking actions.

Reserve capacity before committing.

A booking hold protects capacity while the user completes the next step. Mutations use an Idempotency-Key so a retry does not become a second action.

POST /api/v1/booking-holds
Idempotency-Key: example-request

201 Created
{ "holdId": "example-hold" }

Illustrative product preview

Coordinated modular components representing Oleta’s shared service engine
Service engine · concept imagery

Your service.
Your interface.

A customer website, a native app and a staff portal can use the same offerings, resources and availability rules. Oleta keeps booking operations behind a shared API.

Model people, rooms or equipment as resources. The frontend determines how customers discover a service; Oleta handles the capacity and reservation lifecycle underneath.

Customer surfaces

Connect your website or app to availability, holds and reservations.

Staff tools

Use the same operational model for staff-managed bookings and changes.

Discuss your integration

Questions about Oleta

Do I have to use a particular frontend?

No. Oleta is headless. Websites, native clients, portals and kiosks can use the service engine while keeping their own interface.

What is the difference between a hold and a booking?

A hold temporarily reserves capacity. Confirmation converts a valid hold into a booking through the booking lifecycle.

How are retries handled?

Booking mutations require an Idempotency-Key. The client should preserve that key when retrying the same intended action.

Is this demo connected to live inventory?

The interactive lifecycle example on this page is local and does not create reservations. Follow the reference-site links to explore the existing product surfaces.

Get started

Integration support

Discuss API contracts, SDK integration and your service requirements.

Talk to Systems

Product integration

Discuss connecting your website, app, kiosk or staff portal.

Discuss Oleta

Talk to
Pajic Systems.

Tell us what you need to build, connect or operate.

Contact Systems