Prototype. This is a demonstration support portal built on the Zforce platform for evaluation by Evvo Labs. It is not an official Evvo Labs channel and does not connect to any live ticketing system.

How can we help?

Search the knowledge base, ask our AI assistant, or raise a service request with the engineering team.

Support operates Mon–Fri, 9:00–18:00 SGT. Critical incidents are handled 24/7 through your contracted escalation path.

Service lines

Evvo Labs delivers end-to-end digital ecosystems for government agencies, enterprises, educational institutes and SMEs across Southeast Asia. Pick the area your request falls under — it routes to the right engineering team.

Cybersecurity

Cloud security, threat detection, vulnerability management, SOC operations and infrastructure security.

GovTech bulk tender

Infrastructure & Cloud

Architecture, migration and managed operations across AWS, Alibaba Cloud and Azul platforms.

AI & Data Analytics

Data platforms, analytics pipelines and applied AI for decision support.

Digital Transformation

Moving from legacy estates to emerging technology, including 5G and data intelligence.

System Integration

Connecting platforms, middleware and line-of-business systems into one estate.

Digital Media

Media production and delivery services.

GovTech bulk tender

IoT Solutions

Connected device deployments, gateways and telemetry.

Mobility

Mobile applications and enterprise mobility management.

Blockchain & DLT

Distributed ledger solutions and smart-contract delivery.

IT Solutioning

Advisory, architecture and solution design engagements.

Business Process Outsourcing

Managed teams and operational support functions.

Knowledge base

Type in the search box above to filter these.

How do I raise a support ticket, and what happens next?

Use the service request form below. Include the system affected, when the problem started, who is impacted and which environment (production, staging, development) it is in.

Your request is acknowledged, assigned a severity, and routed to the engineering team that owns that service line. Severity drives response time, so be accurate about business impact rather than defaulting to critical.

How is severity decided?

Critical — a production service is down or a confirmed security incident is in progress. Business operations have stopped.

High — major function degraded or unavailable, with no reasonable workaround, affecting many users.

Normal — standard requests, changes and questions, or a fault with a workaround in place.

If you believe data has been exfiltrated or systems are actively compromised, do not wait for a portal response — use your contracted 24/7 escalation path.

We think we have a security incident. What do we do first?

Preserve evidence before you remediate: do not wipe or rebuild the affected host, and do not power it off if memory artefacts may matter. Isolate it from the network instead.

Capture the alert reference, affected hostnames or asset IDs, the time and timezone the activity began, destination addresses and ports, and any containment already carried out. Never paste passwords, tokens or sensitive payloads into this portal.

Then raise a Critical request under Cybersecurity, or escalate through your contracted incident-response channel if operations have stopped.

A staff member received a suspicious email. How should we report it?

Do not forward the message as an attachment chain or click anything in it. Report it with the sender address, subject line, time received, and whether anyone clicked a link or opened an attachment.

If someone did interact with it and entered credentials, treat it as a Critical request and reset those credentials immediately.

What does a cloud migration engagement involve?

Typically a discovery and assessment of the current estate, a target architecture and landing zone design, a migration plan sequenced by dependency and risk, then execution with rollback points and a managed-operations handover.

We work across AWS, Alibaba Cloud and Azul. Assessment findings and the cost model are produced before any migration work begins.

How often should we run vulnerability assessments?

Continuously for internet-facing assets, with scheduled full-estate assessments at a cadence set by your compliance obligations and rate of change. Remediation windows are agreed per severity band.

Scanning is only half of it — the value is in triage and remediation tracking, which is what our vulnerability management service covers.

Can government agencies procure through an existing tender?

Evvo Labs is a winner of Singapore GovTech's bulk tender in Cybersecurity and Digital Media. Agencies should confirm current eligibility and scope with their procurement team, and we can supply the supporting documentation.

How do I request access for a new team member?

Raise a Normal service request with the person's name, role, start date, the systems they need and the approver. Access requests need approval from the system owner on your side before we provision.

Offboarding should be raised the same way, ideally in advance of the last working day.

Where do I check for planned maintenance?

Planned maintenance windows are communicated in advance to your named contacts. This portal does not display live system status — if you suspect an unannounced outage, raise a Critical request so it can be confirmed.

What information should I not put in a support request?

Never include passwords, API keys, tokens, private keys, full personal data sets or customer records. Sanitise logs before attaching them.

If evidence genuinely requires sensitive material, say so in the request and it will be collected through a secure channel instead.

Raise a service request

Give us enough to act on without a follow-up round trip. Do not include passwords, keys or sensitive data.

Critical means operations have stopped. If a security incident is actively in progress, also use your contracted 24/7 escalation path.