Practical answers before we get started.

Yes. We can own a defined project, add expertise in an area such as Kubernetes or AWS, or help with an ongoing engineering workload. We agree responsibilities with your team so everyone knows who is delivering the work and who makes the decisions.

We start with your objectives, current environment and the people involved. Together, we agree the scope, technical lead, access requirements and first priorities. We also establish how progress will be shared and how changes will be reviewed. The sequence and timing depend on the engagement.

It can include platform changes, upgrades, delivery pipelines, operational issues and optimization. We agree the environments covered, priorities, communication channels and support hours for your engagement. You have a named technical lead and regular updates on the work.

We plan the handover or continued support as part of the engagement. That includes agreeing which configuration, documentation and operational guidance your team needs. If you want ongoing help, we define the next scope and responsibilities together.

Yes. We work on defined projects as well as ongoing support. A migration, Kubernetes implementation or pipeline improvement can be scoped on its own. Tell us the change you need to make, and we will discuss a suitable starting point.

A short description of your environment, the problem or planned change, and any important timing or constraints is enough to start. You do not need a complete technical specification. We can help turn the initial requirement into an agreed scope.

We discuss the technical work, dependencies, responsibilities and level of ongoing involvement before agreeing commercial terms. A defined implementation and a continuing support engagement have different needs, so the proposal reflects the work you actually need us to own.

Our Israel-based team collaborates with North American customers during US business hours. Support coverage, response expectations and escalation arrangements are agreed for each engagement. Tell us about any after-hours requirements when we discuss the scope.

You can discuss an AWS engineering project or ongoing DevOps support with us independently of AWS resale. If billing through Project Circle is also relevant, we explain the included benefits and any separately scoped engineering work before you decide.