Frequently Asked Questions
Below you’ll find detailed answers about how we scope, build, deploy, and support software systems, cloud platforms, and enterprise infrastructure. If your question isn’t here, reach us anytime—our architects are happy to help.
On this page
General
Who we are, what we do, and how we engage.
What does URU Systems do?
URU Systems (SMC-Private) Limited is a software development, cloud integration, and IT consulting partner. We design and build web applications, APIs, data backends, and DevOps platforms; integrate with AWS/GCP/OCI; and deliver enterprise architecture, security hardening, and performance tuning.
Typical roles include DevOps and Systems Engineers, Full-Stack and WordPress/PHP Developers, Database Engineers, Backend API Developers, UI/UX Designers, Solutions Architects, and Enterprise Architects.
Do you work with startups or only enterprises?
We support both. Startups lean on us for speed and pragmatic architecture; enterprises count on our compliance-minded delivery and reliable operations. Our teams adapt process, documentation, and tooling to your stage and governance requirements.
Where are you based and how do we communicate?
We’re headquartered in Gujrat, Punjab, Pakistan. We collaborate globally via Slack/Teams, Zoom/Meet, GitHub/GitLab/Bitbucket, and secure cloud accounts. We provide progress updates on a cadence that matches your project plan (e.g., daily standups or weekly checkpoints).
Engagement & SOW
How we scope, estimate, and structure work.
How do we kick off a project?
We start with a short discovery call to understand goals, constraints, environments, and timelines. We then propose a Statement of Work (SOW) detailing scope, milestones, acceptance criteria, roles, and commercials. Upon approval, we align tools and access to begin delivery.
Tip: If you already have a brief or technical spec, send it to [email protected] to accelerate the SOW.
Can you work hourly and fixed-price?
Yes. For hourly engagements, you can book roles from our Rate Card. For fixed-price, we define clear deliverables and acceptance criteria in the SOW. Many clients use a hybrid model: fixed for core scope, hourly for changes/expedites.
What if we need to change scope mid-project?
We use a lightweight Change Request process. You’ll get impact on cost/timeline and we’ll proceed only after written approval. This keeps delivery predictable while allowing controlled flexibility.
Pricing, Invoicing & Payments
Rates, invoices, methods, and security.
What are your hourly rates?
Our role-based pricing is posted on the Rate Card & Pricing page. Examples include DevOps Engineer, Senior DevOps, Systems Admin, Senior Systems Engineer, Full-Stack Web, WordPress/PHP, Database Engineer, Backend API Developer, UI/UX, Solutions Architect, and Enterprise Architect.
How do you invoice and when is payment due?
We typically invoice after delivery or at defined milestones/intervals (e.g., weekly/bi-weekly/monthly). Managed services are billed in advance of the upcoming term. Standard payment due date is 7 calendar days unless the SOW specifies otherwise.
See our Payment Policy for details.
What payment methods do you accept? Are you PCI compliant?
We accept major cards where supported by our payment partners, bank transfers/IBFT, and applicable local rails. We are PCI-DSS compliant via certified processors and do not store card PAN/CVV/track/EMV data on our servers. All transactions use encrypted (HTTPS/TLS) channels.
Full details are in our Payment Policy.
Do you offer refunds?
Given the bespoke nature of our work and our “invoice after delivery” model, refunds are not typical. Our default remedy for issues is exchange/remediation—re-work, fixes, configuration adjustments, or a service credit—aligned to your SOW’s acceptance criteria.
Please review our Refund & Exchange / Cancellation Policy.
Security, Compliance & Data
How we protect systems, credentials, and customer data.
How do you handle credentials and environment access?
We follow least-privilege access, rotate credentials, and prefer SSO or temporary credentials. Secrets are exchanged via client-approved secure channels and stored in encrypted vaults. Access is revoked at the end of the engagement or on request.
Do you comply with privacy and security standards?
We implement industry best practices across code, infrastructure, and processes (e.g., hardened images, patching, WAF/CDN, TLS, IAM, key rotation, audit trails). We observe PCI-DSS for payments through certified processors and align our data handling to your policies.
See our Privacy Statement for more.
Do you store or process cardholder data?
No. Card processing occurs through PCI-certified payment processors. We do not store full card numbers or CVV/CVC; where tokenization is used, only non-sensitive tokens and minimal metadata are retained for renewals or receipts.
Delivery, Acceptance & Changes
How we define “done”, test, and manage changes.
What does acceptance look like?
Each deliverable has acceptance criteria in the SOW (functional, non-functional, and documentation). You’ll test within the acceptance window (commonly 7 days if not otherwise specified). If something doesn’t meet the SOW, we remediate and re-deliver.
How are changes requested during development?
We use a documented Change Request with impact on budget and timeline. Once approved, changes are scheduled. Preference changes or new requirements after scope approval are treated as out-of-scope tasks.
Can you collaborate with our internal/third-party teams?
Absolutely. We often co-deliver with internal teams, agency partners, or vendor PS. We’ll align on tools, branching strategy, access boundaries, and incident protocols to ensure smooth collaboration.
IP Ownership & Licensing
Who owns the code, documents, and artifacts?
Who owns the source code and deliverables?
Unless your contract states otherwise, upon final payment for the applicable deliverables, you own the work product we create for you (excluding third-party/licensed components and our pre-existing utilities/templates which may be provided under a permissive license).
What about open-source or commercial licenses?
We use reputable open-source and commercial tools when appropriate. Licenses for those components continue to be governed by their respective terms. If specific licensing constraints apply (e.g., AGPL, seat-based), we’ll flag them in the SOW for approval.
Operations, SLAs & Support
Run-time reliability, incident response, and handover.
Do you offer ongoing support and SLAs?
Yes. We provide managed services and support SLAs (e.g., response/restore targets, on-call coverage, monitoring, backups, security updates). SLA packages and escalation paths are defined in the SOW or service plan.
Can you set up observability and incident response?
We implement logging, metrics, tracing, and alerting through tools like Prometheus/Grafana, CloudWatch, OpenSearch, or vendor platforms—and integrate with your incident tools (e.g., PagerDuty). We can run tabletop exercises and tune thresholds to reduce alert noise.
What does handover look like if we take operations in-house?
We deliver runbooks, diagrams, credentials rotation plans, backups/restore procedures, and knowledge-transfer sessions. We can stay on a light retainer for expert interventions as needed.
Cloud, DevOps & Infrastructure
Platforms, CI/CD, security hardening, and performance.
Which clouds and stacks do you support?
We work across AWS, GCP, and OCI, and on-prem with hypervisors like Proxmox/VMware/XCP-ng. App stacks include modern JS (React/Node), PHP/WordPress, Python, containerized workloads, and databases (e.g., PostgreSQL/MariaDB). We also specialize in high-performance web stacks (OpenLiteSpeed/Nginx), caching, and DB tuning.
Can you build our CI/CD and infrastructure as code?
Yes—Git-based workflows with quality gates, automated tests, vulnerability scans, and promotion pipelines. We codify infrastructure with Terraform/Ansible/Helm and can integrate secrets management, policy enforcement, and pre-deploy checks.
Do you handle security hardening and compliance?
We implement baseline hardening (CIS-aligned where possible), firewalling, least-privilege IAM, TLS everywhere, WAF/CDN, patching, backup and DR strategies, and audit logging. We advise on compliance alignment and help embed security into your build/deploy process.
Policies & Legal
Where to find official terms and how they apply.
Where are your official policies?
- Pricing & Rate Card
- Payment Policy
- Privacy Statement
- Refund & Exchange / Cancellation Policy
- Terms of Service (TOS)
If any policy differs from your signed Master Services Agreement (MSA) or SOW, those documents take precedence.
What happens in case of a dispute or chargeback?
Please contact [email protected] first—we resolve most issues quickly. For services that meet the SOW or are accepted/deemed accepted, chargebacks are unwarranted and will be formally contested with documentation (delivery logs, acceptance, communications) as per our Payment Policy and Refund & Exchange policy.








