FAQ

The licence itself is identical — the difference is everything around it. Buying through us, the licence is registered officially in your company's name, we handle installation and configuration, we track the expiry date and warn you well before it, and we deal with the manufacturer on your behalf when a technical issue comes up.

It depends on scope. Supplying and installing a single server takes three to seven working days after delivery. Configuring a firewall for a mid-sized network takes two to three days. Software projects start at six weeks for a first usable version. You get a written timeline with the quotation.

The appliance keeps routing traffic, but it stops receiving updates to its protection and threat rules — in other words it becomes a wall with nobody watching it. We track our customers' licence expiry dates and give at least a month's notice.

In most cases, yes. Kaspersky and Sophos licensing allows devices to be added during the term, priced pro rata for the remaining period. Tell us the number you need and we will send the difference.

Yes, and we state it explicitly in every product description. Refurbished servers are a sound economical choice for non-critical environments or as standby hardware, and they carry a warranty from us. For critical production systems we normally recommend new hardware with the manufacturer's warranty.

Prices are indicative and vary with the configuration requested, the number of licences, the support term, and the exchange rate at the time of order. That is why most products show "Price on Request" — we send a detailed quotation within one working day.

No. That figure means the infrared illumination reaches roughly that far, not that the picture is good enough to identify a face there. Identification needs a closer camera, a longer lens or a higher resolution. That is why the survey asks what each camera is for: identifying a face, reading a number plate, or following general movement. If the purpose is identification and the point is far, we will tell you it needs an extra camera rather than promise something the footage will not show.

You do. The NVR and app credentials are handed over in writing with the handover documents, and we recommend you change them afterwards. Some companies keep the password so the customer stays tied to them; the result is that the owner cannot export a clip during an urgent incident without waiting for someone to let them in. We do not work that way — if we are called back for maintenance, we ask you for access then.

The internet has nothing to do with recording; recording happens on the NVR on site, and an internet outage only stops phone viewing until it comes back. Power is another matter: when it goes, recording stops entirely unless the NVR and the switch are on a UPS. We raise this at the survey because it is an extra cost line — and an easy one to drop from a quotation to make it look cheaper.

It depends on the lock type, and that is a decision we take with you and put in writing before installation. The common magnetic lock releases when power is cut, because life-safety rules require people to get out in a fire — which means, bluntly, that cutting power to the door opens it. The other type stays locked, protecting the room but potentially trapping whoever is inside. We fit a backup battery at each point and hand you a sheet saying which type went on which door, and why.

No. Some people never read reliably, and the problem is worse with manual work that wears fingertips down — factories, kitchens, workshops, construction. The answer is not retrying every morning at a door with a queue behind it; it is a card or face enrolment for those staff specifically, and one device can accept more than one method. We would rather say this before you buy than after.

Not before we have seen it. If it accepts a file import or has an API, we connect it and match the export format to what it takes. If it is closed, the answer is a ready attendance file uploaded by hand each month — and we say so at the start rather than let you find out after installation. Some systems also need their own vendor to cooperate, at a cost on their side, which is outside our control. Send us the system name and we will tell you what is actually possible.

The part that runs over the internet stops: outside calls over SIP, and anyone working away from the office. Internal calls between departments keep working if the PBX sits in your office and your network is up. That is why we ask on the first visit about a backup or landline route for outage hours, and price it in the quotation. If the system is fully cloud-hosted, an internet outage means no phones at all — we say so before the sale, not after.

Not any system. Integration needs the CRM to expose an API or a ready-made connector for the PBX. Where that exists, the link is straightforward. Where the CRM is closed or old with no interface, the only route is a middleware layer — extra development with its own time and cost, and sometimes not worth it. We check your CRM before quoting and tell you which case you are in, rather than discovering it after delivery.

Administrator credentials are handed over in your company's name, and recordings stay on your side. Adding an extension, changing an IVR prompt or shifting the routing hours are things we train your supervisor to do without us. What usually stays with us is version upgrades, line problems with the operator, and larger changes to the call flow. If you end the contract, the system and its data remain yours.

It depends on the heat load and the hours of operation. A room with one or two machines in an office that works by day may be fine with a good ordinary unit — bearing in mind it is not built to run continuously and does not control humidity. A room that runs around the clock, or holds a full rack, will find the ordinary unit cuts out at the worst moment. We calculate the load and tell you which of the two suits you, even when that is the cheaper one.

A UPS is sized against the real load and the runtime required. In practice it is a way to shut systems down safely, or to cover the gap until the generator starts — not a substitute for a power supply. If the business cannot tolerate stopping during a long outage, the answer is a generator, and we say so from the start. UPS batteries are also a consumable: they weaken over time and need testing and replacement, a recurring cost we put in the quotation.

Most of it, yes: the rack, the cabling, the cooling and the door access go in with the room live. But some steps cannot be done without planned downtime — moving the machines into the new rack, connecting the distribution board, and putting the UPS on the line. We identify those steps in advance and schedule them in an agreed window outside working hours, with everything prepared beforehand so the window stays as short as it can be.

Yes. The domain and hosting are registered in your company's name from day one, and you receive the site code and every login. You can move the site to another provider, or hand it to another developer, without asking us and without us being able to hold it up. We keep nothing that makes staying with us compulsory.

The build is a one-off price, but there are recurring costs you should know before signing: the domain renews annually, hosting is ongoing, and later development or new pages are billed separately. Maintenance and changes are not inside the build price unless a written contract says so. We list these items in the quotation rather than letting them surface after handover.

No. The site is built with a separate field for every piece of text in each language, and both versions are entered by hand. That does mean the English needs real copy: either you supply it, or we agree a cost to write it, or we launch in Arabic and add English later. What we will not do is run the Arabic through a translation engine and call the result a bilingual site.

The domain and hosting are in your company's name from day one, and you hold the full administrator credentials. Products, customers and orders can be exported as readable files, and we hand a copy of the database and the store files to whoever you choose to work with next. We hold nothing back that would stop you moving.

The contract is between your company and the bank or payment provider directly, because the merchant account and the settlements are in your name. Approval, how long it takes and which documents are required are the provider's decision, not ours. The commission is deducted from every transaction and is borne by you; it is separate from what the build costs. Our part is to connect the gateway to the store and test real transactions before launch.

No. Sales depend on the product, the price, the stock and the marketing, and Google decides its own rankings. What we can commit to is what we control: a fast store, a sound URL and product-description structure, payment and shipping integrations that have been tested with real transactions, and reports that show you where you stand. Anyone promising you a ranking or a sales figure is selling you talk.

You do. The Google Play and Apple Developer accounts are opened in your company's name and stay under your control, and the signing keys are handed over with them. At delivery we transfer the code repository together with the database and API documentation, so another developer can take the work over without us. We keep nothing that forces you to stay with us.

It does not stop the next day. The version already installed on users' phones keeps working. But the Apple Developer membership renews annually and you pay Apple directly; if it lapses, the app disappears from the App Store. The Google Play registration fee is paid once, though Google requires published apps to keep up with newer Android releases, so an app that stops being updated gradually stops reaching new devices. And with every Android or iOS release a library can break or a store policy condition can change, so the app needs an update. We say this before you sign, not after.

It depends on what that system allows. If it has a documented API or readable database access, the integration is direct and we test it against real data before launch. Closed systems need either the vendor's cooperation or an intermediate layer we build ourselves, and that is extra time and cost, which we price before you sign. Send us the system's name and version and we will tell you which of the two cases you are in.

It is set out in writing in the contract, according to the agreed service level. Critical faults that stop work carry a shorter response time than routine requests. We do not make undocumented verbal promises.

Yes. Remote support is available in every governorate, and on-site visits are arranged according to location, with the cost set out in the contract before signing.