FAQ
Common questions
The questions prospects ask most often. If yours is not here, email us — we will add it.
How do engagements typically start?
With a short discovery call to understand your situation. From there we propose a focused assessment, or if you already know what you need, a scoped engagement plan. Most projects begin within 1–2 weeks of first contact.
How long does a typical engagement run?
Assessments are 1–2 weeks. Focused builds are typically 4–12 weeks. Retainer relationships are ongoing. We are not interested in indefinite billing — every engagement has a clear endpoint or a reason to continue.
Do you work remote or onsite?
Remote-first. We work async-friendly with your team via Slack, GitHub, and standard collaboration tools. Onsite visits for kickoffs or critical milestones are possible by arrangement.
What time zones do you cover?
We work primarily on Central European Time and have natural overlap with the UK, Europe, and US East Coast. For other time zones we adjust schedules to ensure meaningful overlap with your team.
Do you augment our team or work independently?
Both. Some engagements are advisory — we design and review while your team executes. Others are embedded — we work as part of your team for the duration. We will recommend the right shape based on your goals on the discovery call.
What happens to the work after you leave?
Everything is yours: the code, the infrastructure, the documentation, the runbooks. We design for handover from day one. No lock-in, no proprietary frameworks. Your team should be able to run and evolve what we build without us.
How do you handle confidentiality and security?
We sign NDAs and DPAs as standard. We never share client specifics without permission. For sensitive infrastructure access we follow least-privilege and use short-lived credentials.
What if we are not sure what we need?
That is common. Start with a discovery call — no commitment — and we will help you frame the problem. If a focused assessment makes sense, we can do that as a small first step before any larger commitment.
What technology stacks do you specialize in?
AWS, GCP, and Azure for cloud. Kubernetes, Terraform, GitHub Actions, and Argo CD for delivery. Prometheus, Grafana, and OpenTelemetry for observability. Most modern backend languages and frameworks for software work. If your stack is unusual, ask — we will be honest about fit.
How do we get started?
Email ras@advena.io or use the contact form. Include a few sentences about what you are working on. We will reply within one business day to set up a 30-minute discovery call.
Let's build something awesome.
Tell us about your infrastructure or product challenge. We'll reply within one business day.