FREQUENTLY ASKED QUESTIONS

We're an immersive technology studio, and our work falls into four areas. XR & Games: augmented, virtual, and mixed reality apps, full game titles, and 360-degree virtual tours. 3D Visualizations: photorealistic renders, product configurators, architectural walkthroughs, and 3D assets ready for production. AI/ML & Computer Vision: custom machine learning models, natural language features, and real-time vision pipelines for detection, tracking, and spatial mapping. Cloud & DevOps: infrastructure on AWS, GCP, and Firebase, CI/CD pipelines, and real-time multiplayer backends. Most projects pull from more than one of these, and you work with a single team the whole way through.

We ship on all the major spatial computing platforms: Meta Quest 2, 3, and Pro, Apple Vision Pro, Microsoft HoloLens 2, mobile AR on iOS (ARKit) and Android (ARCore), and WebXR experiences that run straight from the browser with nothing to install. For games we also target iOS, Android, PC, and console. We build mostly in Unity and Unreal Engine, with three.js for web-based 3D. If you're not sure which platform fits your audience and budget, that's exactly what our discovery phase sorts out. We prototype on whichever platform gives you the most reach for the least friction.

Both, and they feed each other. We handle full-cycle game development (concept, game design, art, programming, QA, and store submission) for mobile, PC, and console using Unity and Unreal Engine, with titles published on the Apple App Store and Google Play. On the enterprise side we bring the same real-time craft to training simulators, virtual tours, and interactive product experiences. You get game-grade polish either way: tight performance budgets, interaction feedback that feels responsive, and content pipelines that let your team keep the experience fresh after launch.

We build AI that does real work for your business. That usually means a custom machine learning model trained on your data, a natural language feature like an assistant or document intelligence, or a real-time computer vision pipeline that detects, tracks, and maps things. Because we also build XR, we're especially good where vision meets 3D: hand and body tracking, scene understanding, and AI-driven behavior inside immersive experiences. And we take models well past the notebook stage, with optimization for edge and mobile inference, API design, deployment, and monitoring in production.

Yes. We build cloud infrastructure on AWS, Google Cloud, and Firebase, and we set up CI/CD pipelines so releases ship reliably instead of heroically. That covers serverless APIs, real-time multiplayer backends, data stores, authentication, monitoring and observability, and keeping costs sane as you grow. For products we build, one team owns the whole experience, from headset to server. For products you already run, we can audit and harden what's there. At handover you get your infrastructure configuration and documentation, or we keep running it under a support arrangement. Whichever you prefer.

Real-time and XR: Unity, Unreal Engine, ARKit, ARCore, WebXR, and three.js. 3D content: standard modeling, rendering, and optimization pipelines that produce assets for both real-time and pre-rendered use. AI/ML: Python with frameworks like PyTorch, TensorFlow, and OpenCV for vision work. Web: modern TypeScript stacks (this site itself runs on Vue 3). Cloud: AWS, Google Cloud, and Firebase, with containerized and serverless architectures and automated CI/CD. We pick tools to fit the product, not the other way around, and we'll tell you when the boring choice is the right one.

Every project moves through three phases. Discovery: we get aligned on goals, users, platforms, and technical constraints, then hand you a concrete scope, timeline, and estimate. For complex builds this can include a short feasibility prototype. Build: we work in one-to-two-week sprints with a demo or playable build at the end of each one, so you watch the product take shape instead of waiting for a big reveal. QA and on-device testing run the whole time. Launch: store submission or deployment, performance hardening, and analytics. After launch we stay available for support, maintenance, and the next round of work.

It depends on scope, but here are some honest ranges. A focused prototype or proof-of-concept usually lands in four to eight weeks. A production mobile AR app or mid-sized game typically takes three to six months. Large multi-platform titles and enterprise rollouts run six months and beyond. 3D visualization packages are often faster, from a few days to a few weeks per asset batch. Two things keep our timelines honest: a real discovery phase before we commit to dates, and sprint demos that surface any drift early instead of at the deadline. You get a specific timeline with your proposal, not after you sign.

We use two models and recommend whichever one fits your situation. Fixed-price works when the scope is well defined: you get a quoted price tied to specific deliverables and milestones. Time-and-materials or a dedicated-team arrangement works better when the product is going to evolve as we learn: you get a predictable monthly rate and the freedom to reprioritize. A lot of clients start with a small fixed-price discovery or prototype, then continue on a retainer once the direction is clear. You'll get a clear estimate after a scoping conversation, and you won't be charged anything before we agree on one.

Often in your favor. Our team works several hours ahead of US Eastern time, so our late afternoon and evening overlap your morning. That means standups, demos, and decision calls happen during your business hours. European clients share most of their workday with us. The offset also means progress keeps going while you sleep: questions you answer in the morning unblock work that's finished before you're back at your desk the next day. You get close to round-the-clock coverage, with written async updates so nothing depends on catching someone online.

You do. Our client agreements are set up so that, once you've paid in full, the deliverables we create for your project (source code, 3D assets, designs, and documentation) are assigned to you. Ozaar keeps ownership only of pre-existing internal tools, libraries, and know-how that predate your project, and you get a license to use those within your product. The specific terms live in the service agreement we sign together. The Terms of Service published on this website cover the website itself, not client engagements. If your legal team has a preferred IP framework, send it over. We're used to working within client paper.

Yes, and we're happy to do it before you tell us anything sensitive. We regularly sign mutual NDAs with startups protecting an unannounced product, studios guarding a game concept, and enterprises with regulated data. Use your template or ours. Confidentiality shapes how we work day to day too: access to your code, models, and data is limited to the people on your project, and we won't feature your work in our portfolio without written permission. If a public case study is ever on the table, that's a separate conversation, and you control it.

Yes. Rescue work is a regular part of what we do. We start with a technical audit: architecture, code quality, performance on target devices, asset pipeline, and store or platform compliance. You get a written findings report with a prioritized plan, and it's yours whether or not we keep working together. From there we either stabilize and extend the existing code or recommend a focused rebuild of the weak parts. We're deliberately conservative about rewrites. Unity and Unreal projects, mobile apps, and cloud backends that have outgrown their first version are all familiar territory for us.

Every project includes a warranty window after launch, during which we fix defects in our work at no charge. After that, most clients move to a monthly maintenance arrangement. It covers OS and headset compatibility updates (App Store, Google Play, and Quest platform requirements change constantly), plus performance monitoring, content updates, and a pool of hours for small improvements. We agree on the support scope and response expectations in writing before launch, so there's no ambiguity when something needs attention. If you'd rather take maintenance in-house, we hand over documentation and train your team instead.

Three ways, and all of them reach the same humans. Book a free 30-minute intro call through our scheduling link, and bring whatever you have, from a napkin sketch to a full RFP. Send the contact form on this site with a few sentences about your project, timeline, and goals. Or email info@ozaarxr.com directly. We usually respond within one business day. If you need an NDA before sharing anything, just say so and we'll sign one first. From that first conversation to a written proposal is usually one to two weeks, depending on scope.