Cloud migration and platform engineering for enterprise IT teams

Questions IT leaders ask us

• What does SEYA Group do?

  SEYA Group is a cloud consulting and engineering firm in Vancouver, British Columbia. Its engineers plan and carry out cloud migrations, build platform engineering and DevSecOps pipelines, modernize legacy applications, and set up data platforms for mid-size and enterprise IT teams. The architects who scope an engagement are the same people who write the code and sit in your change reviews.

  See the services, grouped by the problem they solve

• Which cloud platforms and tools does SEYA work with?

  SEYA works on AWS, Microsoft Azure, and Google Cloud, and recommends the platform that fits your estate, licensing, and team skills. Infrastructure, configuration, and pipelines are delivered as code with tools such as Terraform, Packer, Ansible, Jenkins, and GitHub Actions. Container work has used Docker and Kubernetes, and application work has covered Java, Node.js, Python, and PowerShell.

  How a cloud platform and migration engagement runs

• Who does SEYA work with?

  SEYA works with IT teams in mid-size and enterprise organizations. Typically that means a CIO or CTO deciding whether to leave the data centre, or a head of infrastructure who has a migration date and an incomplete inventory. Published case studies cover Boeing, Broadcom, LiveRamp, Clearly, and BuildDirect.

  Read the case studies

• How does an engagement with SEYA start?

  It starts with a scoping or assessment call in which you describe the estate, the deadline, and the constraints, and SEYA says what discovery would need to cover and who should be involved. Discovery then works from the inventory, bills, and documentation you already hold, and produces a written design, cost estimate, or brief for your team to review. If the open question is still whether to move at all, the first engagement is cloud adoption.

  What a cloud adoption engagement produces

• Does SEYA work alongside our in-house team, and what happens at handover?

  Yes. SEYA engineers work in your repositories, tools, and review process, and your operators review designs and sit in on cutovers. Handover is part of the scope: you receive the documented architecture, runbooks, code, and working sessions with your engineers, so the platform does not depend on SEYA after the engagement ends.

  Scoped engineering capacity with hand-back planned early

• Who owns the code and the cloud accounts?

  You do, from the start. Cloud accounts are opened in your organization and billed to you, infrastructure code lives in your repositories, and SEYA works through access you grant and can revoke. Written outputs such as an adoption case or cost model are yours to reuse internally or with another supplier.

  Who owns the accounts and code on a migration

• What kind of work has SEYA done before?

  SEYA moved Boeing's GoldCare application stack to Azure on infrastructure vetted by Boeing InfoSec, built Broadcom's Google Cloud environment and moved its API management platform off AWS, designed LiveRamp's first Google Cloud foundation, migrated Clearly's e-commerce platform from Rackspace and on-premises servers to AWS, and built BuildDirect's CI/CD pipeline on the Microsoft stack. Each case study describes what was delivered and the tools used. Results are described qualitatively unless a client has approved a figure for publication.

  Clearly: an AWS migration set up for peak season

• How do we get in touch with SEYA?

  Email hello@seyagroup.io, call +1 (778) 819-0148, or use the enquiry form on the contact page. SEYA's office is at 401 - 68 Water St, Vancouver, BC. Come with the question you have been asked and a description of the estate, and the first call will set out what discovery would need to cover.

  Send an enquiry through the contact form