Engagement Models — How We Work, How We Charge, and How Fast We Start.

It depends on the model and the scope, and we don’t publish a rate card. The main cost drivers are target scale, architecture (P2P, SFU or a custom media server), compliance requirements, integrations, the number of platforms, and how much of the product already exists. Builds get a firm, itemised estimate after a free technical scoping call. Rescue and scaling work gets a prioritised plan within two weeks, before you commit.

We reply within 24 hours and set up a free 30-minute technical scoping call. A fixed-scope first step can follow straight after: an architecture review takes 1–2 weeks, and a rescue assessment delivers a root-cause plan within two weeks. In one rescue, we transferred a full engineering team to the client in a single week.

Choose fixed price when requirements are clear from day one, such as an MVP, a prototype or a well-specified feature, with milestone-based payments. Choose Time & Materials when scope will evolve or the work starts with diagnosis, as in a rescue, where the exact fix only emerges once we’re inside the code. For long-lived products, a dedicated team billed monthly is usually the better fit than either.

You do. All source code, documentation, architecture diagrams and intellectual property transfer to you, and we can work under your preferred IP agreement. Every engagement also ends with architecture documentation and knowledge transfer, so owning the code means your team can actually run it. Conversations can start under an NDA before you share anything.

Yes to an NDA, before you share any details. For EU projects where we process personal data on your behalf, we sign a GDPR Data Processing Agreement. For US healthcare work involving protected health information, we sign a Business Associate Agreement, and we design the platform so every other vendor in the PHI path is covered too.

Yes, and we usually recommend it. An architecture review takes 1–2 weeks and gives you a documented blueprint and cost model. A rescue assessment gives you a root-cause diagnosis and a prioritised plan within two weeks. A proof of concept tests the riskiest part of the architecture on real networks or real data. Each answers a concrete question before you commit to a build.

Not unless you choose to. You own the code, and every engagement includes architecture documentation and knowledge transfer so your team isn’t dependent on us for basic operations. If you want to bring the platform in-house, we document everything and hand it over. Most clients do keep an ongoing dedicated team for 1–3+ years, because the foundation makes continued development efficient.

Yes. Embedded consulting puts WebRTC and video specialists next to your team for architecture guidance, code reviews, pair programming and real-time help with WebRTC-specific problems. Your team builds, and we keep them unblocked. If you’d rather hand over a whole workstream, a dedicated Trembit team can own it while your engineers stay on the rest of the product.

For standard video calls, a CPaaS such as Twilio or Agora can be the right choice, and we’ll say so. A specialist team matters when the platform becomes the constraint: KBV certification (which rules out third-party media routing), custom recording pipelines, per-minute bills growing faster than your user base, or failures below the SDK that need protocol-level debugging. We build on managed platforms and on owned infrastructure.