Local-first deployment

An offline Jyotish engine path for products that cannot depend on a connection.

If your application needs calculations on the device, evaluate a native engine licence separately from hosted API access. Platform binaries, size, coverage and redistribution rights must be confirmed in a written technical and commercial scope.

Why local calculation

Put the critical calculation path where your users are.

A local runtime can be relevant to unreliable networks, privacy-sensitive products and predictable on-device behavior. Suitability depends on the exact platform and feature set tested—not a general promise that every API endpoint runs offline.

Connectivity resilience

Design workflows that do not require a round-trip for every calculation, subject to the licensed runtime's coverage.

Local data handling

Evaluate whether sensitive birth inputs can remain on the user's device in your intended architecture.

Integration control

Define your own interface, cache and release process around the calculation component.

What to ask for

Make the licence technically testable.

The source documentation verifies a Formula-Lite provider built on VSOP87 series arithmetic. It does not, by itself, prove that a packaged public SDK is ready for every mobile platform. A meaningful evaluation should include evidence for your target environment.

  • Target platforms: Android, iOS, desktop or embedded, with exact ABI and language binding.
  • Coverage: date span, astronomical bodies and Jyotish calculation families.
  • Validation: reference cases, edge dates, location and timezone handling.
  • Commercial terms: source/binary delivery, redistribution, updates and support.
Platform briefOS · ABI · app type
Technical evaluationSize · tests · coverage
Written licenceDelivery · rights · support
Availability note: This page invites a private evaluation. It does not offer a public SDK download, assert an exact binary size, or claim that all hosted API endpoints run offline.
Frequently asked

Offline engine questions

Is the offline engine the same purchase as API access?

No. On-device distribution and hosted API use have different technical and commercial implications, so they need separate scoping.

Can I embed it in a mobile app?

Ask for a platform-specific evaluation. Do not rely on a claimed size or compatibility until the exact build is tested on your targets.

Will it replace all server calls?

That depends on the licensed calculation coverage and your own product architecture. The enquiry should specify which operations must be offline.

Tell us where your engine must run.

Send platform, required calculations, offline constraints and distribution model.

Send an evaluation brief ↗