Frequently asked questions.

Custom software, AI platforms, mobile apps, hospital management systems, POS / retail systems, automation, and internal tools. We focus on healthcare, retail, and enterprise operations. Project sizes range from 2-week discovery sprints to multi-month platform builds and ongoing engineering retainers.

Xenara is a Canadian corporation (Xenara Inc.) headquartered in Toronto, Ontario. We're remote-first by design — our team works with clients across Canada, the United States, Pakistan, India, the UAE, Saudi Arabia, the United Kingdom, and other markets on a remote basis.

Yes — we work remote-first with businesses across Pakistan, India, the UAE, and the broader region. We communicate in English and Urdu where useful, support engagements priced in PKR / INR / AED / USD, and design around regional realities (JazzCash / Easypaisa / UPI integration, local print conventions, connectivity profiles).

Senior engineering by default. The people you talk to during scoping are the people who ship the code. We don't hand projects off to junior teams after the sales call. Engagements are typically smaller, faster, and produce production-grade software — not slide decks.

Three common formats: (1) Fixed-scope discovery sprints (2 weeks) for architecture and roadmap; (2) Fixed-fee builds (6–14 weeks) for MVPs, AI integrations, mobile apps, and POS pilots; (3) Monthly retainers for ongoing engineering, platform support, and embedded squad engagements.

Discovery sprints are fixed-fee. Build engagements are fixed-fee, milestone-based, or quoted by complexity. Ongoing retainers are monthly. We invoice in USD, CAD, GBP, AED, PKR, or INR depending on the engagement.

Yes. A 30-minute introductory call is free. We use it to understand what you're building, what's in the way, and whether we're the right fit. If we're not, we'll say so.

For fixed-scope engagements: 30–50% upfront, balance on milestones. For retainers: monthly invoicing, net 14 or net 30. We invoice in USD, CAD, EUR, or PKR depending on the engagement currency.

We default to TypeScript / Next.js / React for web, React Native for mobile, Python or Node.js for backend, and Postgres for data. We use Swift / Kotlin for native mobile when the use case demands it. AI work uses Claude, GPT, Llama, or open-source models depending on requirements. We adapt to the customer's existing stack when that's the right call.

Yes. Full IP transfer is standard. Source code lives in your repositories. Deployments live in your cloud accounts. We don't lock customers into hosted infrastructure they don't control.

Yes — happy to sign your NDA before the first discovery call, or use our standard mutual NDA if you don't have one ready. Both sides come out protected before anything sensitive is shared.

Customer-determined. We support deployments in Canadian regions, US regions, EU regions, customer-managed on-prem servers, or hybrid configurations. Data residency is configured per engagement based on compliance and customer preference.

Yes. We design healthcare deployments with compliance baked in — encryption at rest and in transit, role-based access, audit logging, data residency configuration. Our HMS deployments meet PIPEDA / PHIPA expectations in Canadian provinces and are architected to be HIPAA-aligned where US compliance applies.

Yes — HL7 v2, FHIR, and proprietary EMR APIs are part of typical hospital engagements. We've integrated with provincial health information exchanges, third-party EMRs, lab analyzer feeds, and pharmacy stock systems.

Yes — fully on-prem deployments are common in our Pakistani engagements and available in Canadian engagements where data residency demands it. Hybrid deployments (DB on-prem, app on cloud) are also supported.

Yes. Default: React Native cross-platform. Fully native (Swift / Kotlin) when the project demands it — heavy device integration, ARKit, HealthKit, complex camera or Bluetooth work, or extreme performance requirements.

Yes — store assets, screenshots, privacy declarations, and store submission are part of every mobile engagement. We typically clear store review in 1–2 review cycles.

Yes — QuickBooks, Xero, Sage, and most local Pakistani / Canadian accounting platforms. End-of-day journal entries post automatically. Tax and tendered cash reconcile against accounting from day one.

Yes — offline-first by design. Counter terminals keep selling when the internet drops. Sync resumes automatically when connectivity returns. Essential for stores in areas where broadband isn't guaranteed.

Yes — most of our AI engagements are exactly this. RAG, agents, copilots, and structured-output AI features embedded inside software customers already use. See our AI Development service for the full process.

Production AI does hallucinate. We design around it: retrieval grounds the model in your data, structured outputs constrain what it can return, evals catch regressions, and humans stay in the loop for critical decisions. Critical fields never come from the model alone — they're validated against source data.

Yes — open-source models (Llama, Mistral, Qwen) on customer-controlled GPUs are common when data residency, cost, or compliance demands it.