Documentation

Public docs live

Yekal Booking Public Docs

Use this page to evaluate the Yekal Booking package before you buy. Full technical setup docs ship inside the delivered source repository/source package after verified payment.

Before you buy

Public evaluation scope

This page covers the V1 buyer questions you should be able to answer before checkout.

After verified payment

Full buyer docs

Licensed buyers receive the complete technical documentation bundle inside the delivered source repository/source package.

What buyers receive

Verified purchase unlocks the fixed Yekal Booking Launch License for running one branded booking rollout.

Private source repository access for Yekal Booking.
One-time commercial license for one production deployment under the launch package.
Full technical documentation inside the delivered repository after verified payment.

Setup overview

Expect a standard buyer handoff: accept repository access, review the setup docs, prepare environment values, and validate locally before production.

Accept the GitHub organization or repository access sent after verified payment.
Follow the repository setup guide and environment checklist included with the source package.
Use a local or staging deployment first so you can validate branding, flows, and provider credentials safely.

Deployment expectations

Yekal is sold as self-hosted source code. Your rollout depends on your own infrastructure, provider accounts, compliance review, and release process.

Plan for your own hosting, domains, monitoring, and operational ownership.
Confirm environment variables, secrets, and provider accounts before go-live.
Run staging checks and your own legal/compliance review before routing customer traffic to production.

Customization scope

The public docs cover launch planning, not bundled custom implementation. Buyers can adapt the delivered source to match their own brand and market.

Update copy, branding, pricing, and business rules for your offer.
Scope migrations, custom features, or buyer-specific builds as separate paid work if you need them.
Use the full repository docs to guide deeper UI, workflow, and integration changes.

Provider requirements

The delivered Booking Platform uses provider accounts you control for hosting, domains, email, payments, SMS, analytics, and repository access.

GitHub access is required for repository delivery.
Stripe and Stripe Connect support booking payments and tenant payouts.
Twilio, Resend/React Email, hosting, domain, and monitoring accounts are configured by you for your rollout.

Support boundaries

The launch package includes a limited handoff support window for delivery and documentation questions, not an unlimited implementation retainer.

Pre-purchase questions can go through the public contact channel.
Launch support is limited to handoff, delivery recovery, and documentation guidance unless separately agreed.
Hosting, customer-specific implementation, compliance work, and ongoing operations remain your responsibility unless separately agreed.

Delivery flow

Checkout and delivery stay intentionally separated so source access is only issued after verified payment for the current Booking launch package.

You review the Booking launch package boundaries before completing checkout through Creem.
After Creem verifies payment server-to-server, Yekal sends the delivery email and repository access instructions.
The package covers one commercial deployment and does not add future platform rights unless separately sold.

Signed license setup for buyers

Booking deployments need three buyer-safe environment variables from the delivery email plus Yekal's validation endpoint. Keep the private signing key only on Yekal.

Set these in your Booking deployment

Add the following values to the sold Booking Platform app before staging or production launch.

LICENSE_KEY

The signed license key from your delivery email. The Booking runtime sends this to Yekal during license checks.

LICENSE_PUBLIC_KEY

The Ed25519 public key that matches Yekal's signing key. This key is safe to ship with your deployed Booking app.

LICENSE_API_URL

Point this to Yekal's production validation endpoint so the Booking runtime can verify the signed license.

Deployment env example

LICENSE_KEY="the signed key from your delivery email"
LICENSE_PUBLIC_KEY="the matching public key from Yekal"
LICENSE_API_URL="https://yekal.com/api/license/validate"

Keep this only on Yekal

Do not copy Yekal's server-side signing secret into the sold Booking deployment.

Yekal-only signing secret

LICENSE_PRIVATE_KEY

Yekal uses this private Ed25519 key during verified fulfillment to sign or reissue license payloads.

Buyers should never deploy the private signing key inside the Booking app, CI, or client bundles.
The sold Booking deployment only needs the signed LICENSE_KEY, the matching LICENSE_PUBLIC_KEY, and the LICENSE_API_URL value.
If you need a key rotation or license reissue later, use the delivered repository docs or contact support.

Validation endpoint

The Booking runtime checks licenses against Yekal's validation API rather than trusting a client-only success state.

Production endpoint

https://yekal.com/api/license/validate

/api/license/validate is Yekal's endpoint for verifying license format, signature, and expiry.
For production Booking deployments, set LICENSE_API_URL to https://yekal.com/api/license/validate.
Test the endpoint from local or staging before production so you know the deployed app can reach it.

Current domain behavior

Launch docs stay honest about the current runtime enforcement boundary.

Current signed Booking licenses default to domains: ["*"] until Yekal collects allowed deployment domains during checkout.
The public V1 site does not yet enforce buyer-specific deployment or domain limits at validation time.
Use the launch package for one commercial deployment as the current commercial term; stricter domain registration would require a later collection flow.

Full docs continue after purchase

These public docs answer the pre-purchase buyer questions. The delivered repository continues with the full setup sequence, provider configuration, deployment steps, and troubleshooting guides.

Offer boundaries before payment

Use these docs to validate the commercial boundary, not just the technical setup.

You are buying self-hosted source code, not managed hosting, DevOps, or third-party provider accounts.
Launch support is limited to handoff, delivery recovery, and documentation guidance unless separately agreed.
Custom feature development, migrations, and buyer-specific implementation are separate scoped services.
Yekal does not provide buyer-specific legal, tax, privacy, or compliance guarantees for your rollout.
The public launch package is limited to one commercial deployment unless separately expanded in writing.
The current public package applies to Yekal Booking only, not future platforms or future tiers.

Next steps

Want to validate fit before buying? Review the boundaries above, book a demo, request launch access, or review the secondary purchase path after qualification.

Request launch access Book a demo View purchase path