How it works
From a request to a running platform with valid licenses and a support agreement. This is the process for every order, whether it is a single license or a full project.
Request
You describe what you need: the use case, the expected scale, the software you have in mind or the problem it should solve. By email or through the quote form.
Proposal
Within five business days you receive a proposal: the recommended software and editions, license quantities and terms, the project scope if any, the support level, and prices. For larger projects the proposal follows a call with your engineers.
Agreement
The order is placed under our terms of use or under a project agreement drafted for the customer. Vendor end-user license terms are attached where the vendor requires it.
Invoicing and payment
Licenses are invoiced on order; project work on milestones; support annually in advance. Invoices comply with Serbian and EU requirements, including VAT treatment for cross-border B2B supplies.
License delivery
License keys, activation instructions and the vendor’s documentation are delivered by email within one business day of payment. Each license is registered to the customer’s organisation and listed in a license schedule you can request at any time.
Deployment and acceptance
For projects, our engineers deploy and integrate the software, run the agreed tests with your team and hand over the documentation of the installed system. Acceptance is confirmed in writing.
Support and renewals
Under a support agreement you have a ticket system, defined reaction times and a named engineer. We track expiry dates and send renewal proposals 60 days in advance.
Documents you receive
| Proposal | Software, quantities, terms, scope of work, prices, validity |
|---|---|
| Order confirmation | Confirms the accepted proposal and the delivery dates |
| License schedule | Every license held by your organisation: product, edition, capacity, term, key identifier |
| Invoice | With the supplier details required by law and the VAT treatment applied |
| Acceptance report | For projects: tests performed, results, open items, sign-off |
| System documentation | For projects: architecture, configuration, operating procedures |
| Support agreement | Coverage, reaction times, contacts, escalation path |
License models
The model depends on the vendor and the product. The common ones:
- Perpetual license for a server or an installation, with optional annual maintenance for updates.
- Subscription for a term of one or more years, including updates and vendor support.
- Capacity-based licenses counted in channels, streams, viewers or cameras, extendable during the term.
We explain the model in the proposal and recommend the one that costs least over the expected life of the platform.
Compliance
- Every license is sold with the vendor’s authorisation and registered to the end customer.
- Export control and sanctions screening is performed for every order.
- Customer data is handled as described in the privacy policy; Orbius does not host customer platforms and does not process the video or subscriber data that runs through them.