ZTABS delivers cloud services for Helsinki businesses — AWS, Azure, and GCP migration, infrastructure design, and managed services. Finnish data residency options, GDPR compliant, and built for Nordic enterprise needs.
Cloud services in Helsinki serve Finnish businesses navigating one of the most consequential technology decisions of the decade — where to run their IT infrastructure. Finnish businesses are cloud-mature by global standards (Finland ranking among the top 5 in EU cloud adoption), but maturity brings its own challenges: multi-cloud complexity, cost management, security requirements, and the specific Finnish regulatory and technical landscape. Helsinki cloud services: the factors defining cloud needs in Finland. Finnish data sovereignty: certain Finnish industries require data to remain in Finland or within the EU. Finnish healthcare: Kanta system integration requiring Finnish-hosted infrastructure. Finnish financial services: Finanssivalvonta (Financial Supervisory Authority) guidelines on cloud outsourcing requiring risk assessments and exit strategies. Finnish government: Traficom and DVV (Digital and Population Data Services Agency) guidelines on government data in cloud. Cloud regions: AWS eu-north-1 (Stockholm — closest AWS region to Helsinki, ~50ms latency), Azure Finland (planned/available — check current status), and GCP europe-north1 (Finland — Hamina data centre, lowest latency for Helsinki businesses). Finnish data residency: for maximum sovereignty — GCP Finland (Hamina) providing in-country hosting, or Finnish cloud providers (Telia, Elisa, Hetzner Finland) for workloads requiring Finnish jurisdiction. Nordic cloud landscape: Finnish businesses often operating across the Nordics — Sweden, Norway, Denmark, and Finland. Cloud architecture: supporting multi-country operations while meeting each country's data residency requirements. Nordic integration: connecting Finnish systems with Swedish, Norwegian, and Danish offices, partners, and customers. Finnish connectivity: Finland has excellent internet infrastructure — businesses expecting low-latency, high-reliability cloud connectivity. HaaS (Helsinki as a Service): Helsinki data centres providing colocation and hybrid cloud options for businesses wanting on-premises control with cloud flexibility. GDPR cloud: all cloud deployments in Helsinki requiring GDPR compliance — data processing agreements with cloud providers, data encryption, access controls, and cross-border transfer mechanisms. The Finnish DPA (Tietosuojavaltuutetun toimisto): actively enforcing GDPR — cloud deployments needing to demonstrate compliance, not just assert it.
Helsinki's cloud demand comes from businesses at various stages of cloud journey: (1) Cloud migration: Finnish companies moving from on-premises to cloud. Migration projects: data centre exit (Finnish businesses closing on-premises data centres — migrating workloads to AWS, Azure, or GCP. Finnish data centres: many companies running ageing infrastructure in Helsinki data centres, facing hardware refresh costs and staffing challenges. The decision: migrate to cloud rather than invest in new on-premises hardware), application modernisation (legacy Finnish applications — migrating from Windows Server, Oracle, and on-premises Linux to cloud-native architectures. Finnish legacy: Lotus Notes (still surprisingly common in Finnish enterprise), custom-built ERP systems, and industry-specific software that needs modernisation), SAP migration (moving SAP workloads to cloud — S/4HANA on AWS, Azure, or GCP. Finnish SAP: many large Finnish companies running SAP — the S/4HANA migration creating cloud migration demand. RISE with SAP: SAP's cloud offering — Finnish companies evaluating whether to go with SAP's cloud or run SAP on their chosen cloud provider), and hybrid cloud (Finnish companies wanting some workloads in cloud, some on-premises — typically driven by data sovereignty requirements or legacy system constraints. The hybrid approach: common in Finnish financial services and healthcare where certain data must remain in Finnish jurisdiction). (2) Cloud-native development: Helsinki companies building on cloud. Cloud-native projects: microservices (decomposing monolithic Finnish applications into microservices — Kubernetes orchestration, container deployment, and service mesh. Finnish cloud-native: growing adoption in Helsinki tech companies and digital-first Finnish enterprises), serverless (event-driven architectures — AWS Lambda, Azure Functions, GCP Cloud Functions. Finnish serverless: cost-effective for variable-load applications — Finnish seasonal businesses (tourism, retail) benefiting from pay-per-execution pricing), DevOps and CI/CD (cloud-based development pipelines — GitHub Actions, GitLab CI, and cloud-native CI/CD. Finnish DevOps: Helsinki tech companies adopting DevOps practices — cloud enabling automated testing, deployment, and monitoring), and data platforms (cloud data infrastructure — Snowflake, Databricks, BigQuery, and Redshift. Finnish data: companies building cloud data platforms for analytics, reporting, and AI/ML. Finnish data sources: Netvisor, SAP, Salesforce, and Finnish-specific systems feeding cloud data warehouses). (3) Cloud security: protecting Finnish cloud environments. Cloud security projects: security architecture (designing secure cloud environments — VPC design, network segmentation, IAM policies, and encryption. Finnish security: high standards — Finnish companies expecting security equivalent to or better than their on-premises environments), compliance (GDPR, Finanssivalvonta, and industry-specific compliance in cloud. Finnish compliance: demonstrating to regulators and auditors that cloud environments meet Finnish regulatory requirements), SOC 2 and ISO 27001 (Finnish companies pursuing cloud security certifications — SOC 2 for SaaS companies, ISO 27001 for enterprise. The certifications: requiring cloud security controls, monitoring, and documentation), and threat detection (cloud security monitoring — detecting and responding to threats in cloud environments. Finnish threat landscape: nation-state threats (geographic proximity to Russia), ransomware, and supply chain attacks). (4) Cloud optimisation: managing cloud costs and performance. Optimisation projects: cost management (Finnish companies finding cloud costs exceeding expectations — "lift and shift" migrations often running cloud like an expensive data centre. The fix: right-sizing instances, leveraging reserved capacity, implementing auto-scaling, and eliminating waste. Finnish cost sensitivity: cloud budgets scrutinised carefully — Finnish CFOs expecting clear cloud ROI), performance (optimising application performance in cloud — latency, throughput, and availability. Finnish performance: users in Helsinki expecting responsive applications — cloud architecture designed for low-latency access from Finland and the Nordics), multi-cloud management (Finnish companies using multiple cloud providers — AWS for some workloads, Azure for M365 integration, GCP for data analytics. Multi-cloud complexity: management, security, and cost tracking across providers), and FinOps (financial operations for cloud — tagging strategy, cost allocation, budgeting, and forecasting. Finnish FinOps: cloud costs allocated to business units, projects, and cost centres — enabling data-driven cloud spending decisions). (5) Managed cloud: ongoing cloud operations. Managed projects: 24/7 monitoring (cloud infrastructure monitoring — availability, performance, and security monitoring. Finnish managed: Helsinki businesses wanting European-timezone managed services — not US-based NOCs that are asleep when Helsinki works), backup and DR (cloud backup and disaster recovery — automated backups, cross-region replication, and tested recovery procedures. Finnish DR: recovery from the Stockholm or Ireland region if the primary Helsinki/Stockholm region fails), patching and maintenance (keeping cloud infrastructure current — OS patching, security updates, and application maintenance. Finnish maintenance: automated maintenance windows scheduled outside Finnish business hours), and support (cloud operations support — incident response, change management, and capacity planning. Finnish support: Finnish-speaking or English-speaking support during Finnish business hours, with 24/7 critical incident response).
Our Helsinki cloud services follow a methodology designed for Finnish enterprise requirements: (1) Cloud assessment (weeks 1-2): understanding current state and requirements. Infrastructure audit: cataloguing existing IT infrastructure — servers, applications, databases, storage, and network. Finnish assessment: identifying Finnish-specific systems (Kanta integration, Finnish banking connections, Netvisor/Procountor integration) that have specific cloud hosting requirements. Application assessment: evaluating each application for cloud readiness — cloud-native ready, lift-and-shift compatible, or requiring modernisation before migration. The 6 Rs: rehost (lift and shift), replatform (minor optimisation), refactor (cloud-native rewrite), repurchase (replace with SaaS), retire (decommission), and retain (keep on-premises). Data classification: classifying data for sovereignty requirements — which data must remain in Finland? Which can be in the EU? Which has no geographic restriction? Finnish classification: personal data (GDPR — EU minimum), financial data (Finanssivalvonta — risk assessment required), health data (Kanta — Finnish hosting may be required), and government data (Traficom guidelines). Cost analysis: current IT costs vs. projected cloud costs — enabling data-driven migration decisions. Finnish cost comparison: including all current costs (hardware, data centre, power, cooling, staff, licensing) vs. cloud (compute, storage, networking, management, and licensing in cloud). (2) Cloud architecture (weeks 2-3): designing the target state. Cloud selection: recommending the right cloud for the business. AWS (broadest services, nearest region Stockholm, strong enterprise capability), Azure (best for Microsoft-heavy organisations, M365 integration, growing Finland presence), GCP (Finland data centre in Hamina, strong data analytics and AI/ML), and multi-cloud (multiple providers for resilience, avoiding lock-in, or best-of-breed services). Finnish recommendation: typically based on existing technology stack (Microsoft-heavy → Azure, analytics-heavy → GCP, broad workloads → AWS) and data residency requirements (GCP Hamina for Finnish data residency). Network architecture: connecting Helsinki offices and users to cloud — VPN (site-to-site for on-premises integration), Direct Connect / ExpressRoute (dedicated connections for high-throughput, low-latency workloads), and SD-WAN (for multi-site Finnish organisations). Finnish networking: Telia, Elisa, and DNA providing local connectivity — cloud architecture designing for Finnish ISP integration. Security architecture: cloud security design — IAM (identity and access management), encryption (at rest and in transit), network security (VPCs, security groups, and NACLs), and monitoring (CloudTrail, Azure Monitor, or GCP Cloud Audit Logs). Finnish security: meeting Traficom security guidelines and industry-specific requirements. (3) Migration (weeks 3-8+): moving to cloud. Migration waves: applications migrated in planned waves — starting with lower-risk, lower-complexity workloads and progressing to business-critical systems. Finnish migration: wave 1 (development/test environments), wave 2 (internal applications), wave 3 (customer-facing applications), wave 4 (business-critical and regulated workloads). Data migration: moving data securely — database migration (AWS DMS, Azure Database Migration Service), file migration (large data sets via transfer appliance or network transfer), and application data (coordinated cutover planning). Finnish data migration: ensuring data residency is maintained throughout migration — data not passing through non-EU regions during transfer. Testing: comprehensive testing after each migration wave — functional testing, performance testing, integration testing, and security testing. Finnish testing: testing Finnish-specific integrations (banking, Kanta, Vero) in the cloud environment. Cutover: planned transition from on-premises to cloud — DNS changes, load balancer updates, and monitoring activation. Finnish cutover: scheduled outside Finnish business hours (typically Friday evening to Sunday), with rollback plans tested and ready. (4) Optimisation (weeks 6+): maximising cloud value. Right-sizing: analysing actual resource utilisation and adjusting instance sizes — most cloud environments over-provisioned by 30-50%. Finnish optimisation: right-sizing based on actual Finnish usage patterns (business hours 8:00-17:00 EET, seasonal variation, and monthly peaks). Reserved capacity: committing to 1-3 year reserved instances for stable workloads — 30-60% cost savings vs. on-demand. Finnish reserved: analysing workload stability before committing — avoiding over-commitment on variable workloads. Auto-scaling: implementing automatic scaling for variable workloads — scaling up during peak and down during quiet periods. Finnish auto-scaling: configured for Finnish time zones and business patterns. Cost monitoring: implementing cost tracking and alerting — FinOps dashboards showing daily, weekly, and monthly cloud spend by service, team, and project. (5) Managed services (ongoing): operational support. Monitoring: 24/7 cloud infrastructure monitoring — availability, performance, security, and cost. Finnish monitoring: critical alerts with 15-minute SLA response, standard alerts with 1-hour response. European-timezone management: primary support during Finnish business hours, with 24/7 critical incident coverage. Backup and DR: automated daily backups, cross-region replication for critical data, and quarterly DR testing. Finnish DR: recovery procedures tested and documented — RTO and RPO agreed per application criticality. Patching: automated security patching with change management — patches tested in non-production before production deployment. Finnish patching: maintenance windows agreed with business stakeholders, scheduled for minimal impact. Continuous improvement: monthly cloud review — performance, cost, security, and capacity assessment. Recommendations: proactive recommendations for improvements — new services, better architectures, and cost savings.
Manufacturing / Industrial
A Helsinki-based manufacturing company (€85M annual revenue — producing industrial automation components, 340 employees, 2 factories in Finland, sales offices in Stockholm and Munich) needed to migrate from on-premises infrastructure to cloud. (1) Ageing infrastructure: the company's Helsinki data centre (colocation at Equinix Helsinki) hosting 42 physical servers, 120 virtual machines, and 28TB of data. Infrastructure age: average server age 6.2 years — performance degrading, hardware failures increasing (3 incidents in the past 6 months), and manufacturer support ending for 15 servers. Hardware refresh quote: €480,000 for new servers, storage, and networking — the CFO questioning whether refreshing on-premises infrastructure was the right investment. (2) IT staffing: 3 IT staff managing the on-premises infrastructure — spending 70% of their time on infrastructure maintenance (patching, backups, hardware issues, and vendor management) rather than business-enabling technology projects. IT capability: the 3-person team skilled in Windows Server and VMware — limited cloud experience. The company: wanting IT to focus on business applications, digital initiatives, and supporting the factories rather than maintaining servers. (3) Multi-site connectivity: Helsinki headquarters, 2 factories (Tampere and Oulu), and sales offices in Stockholm and Munich — connected via VPN over public internet. Performance: factory systems (MES, quality management) experiencing 200-400ms latency when accessing Helsinki-hosted applications — affecting production operations. Munich sales office: 350ms+ latency to Helsinki — CRM and ERP sluggish for German sales team. (4) SAP: the company running SAP Business One (hosted in the Helsinki data centre) — the core ERP for financials, procurement, and inventory. SAP performance: degrading as data volume grew — month-end reporting taking 45 minutes, inventory queries taking 20+ seconds. SAP upgrade: the company needing to upgrade SAP Business One to the latest version — the upgrade complex on the current ageing hardware. (5) Disaster recovery: DR limited to nightly tape backup stored at a secondary location. RTO (Recovery Time Objective): 48-72 hours (the time to restore from tape to replacement hardware). RPO (Recovery Point Objective): 24 hours (data loss up to 24 hours). The risk: a Helsinki data centre failure causing 2-3 days of complete business outage — the CFO and CEO considering this unacceptable risk.
We migrated the company to AWS (eu-north-1 Stockholm, with GCP Hamina for specific Finnish-residency workloads) over 10 weeks. (1) AWS infrastructure: cloud foundation. Landing zone: AWS Control Tower establishing a secure, multi-account environment — production, development, staging, and shared services accounts. Network: AWS Transit Gateway connecting all accounts, with VPN connections to factories (Tampere, Oulu) and sales offices (Stockholm, Munich). Performance: factory latency from 200-400ms to 8-15ms (Stockholm region — geographically close to Helsinki). Munich latency: from 350ms to 25ms (AWS backbone routing). Security: AWS Organizations with SCPs (Service Control Policies), IAM roles with least-privilege access, AWS CloudTrail for audit logging, and AWS GuardDuty for threat detection. Finnish security: meeting Traficom guidelines and industry security standards. (2) Application migration: systematic workload move. Wave 1 (weeks 3-4): development and testing environments — 15 VMs migrated using AWS Application Migration Service. Low risk, enabling the team to learn migration processes. Wave 2 (weeks 5-6): internal applications — file shares (migrated to AWS FSx for Windows), email archive, internal tools, and HR system. SharePoint: migrated to SharePoint Online (Microsoft 365) — improving collaboration for the multi-site team. Wave 3 (weeks 7-8): customer-facing and production applications — CRM, customer portal, and quality management system. Database migration: on-premises SQL Server databases migrated to Amazon RDS (SQL Server) — managed database service eliminating database maintenance burden. Wave 4 (weeks 9-10): SAP Business One and business-critical systems. SAP: migrated to AWS using SAP-certified EC2 instances — performance dramatically improved on modern cloud hardware. SAP migration: full testing with Finnish SAP partner to verify all SAP functions, Finnish financial reporting, and integrations. (3) Finnish data residency: GCP Hamina for specific workloads. Requirement: certain customer data and quality records requiring Finnish data residency (customer contracts specifying data remains in Finland). Solution: GCP europe-north1 (Hamina, Finland) hosting specific databases containing Finnish-residency-required data. Integration: AWS Stockholm as the primary platform, GCP Hamina for Finnish-residency workloads — interconnected via private networking. The hybrid: satisfying Finnish data residency requirements while leveraging AWS's broader service catalogue. (4) Disaster recovery: cloud-native DR. DR strategy: multi-AZ deployment in Stockholm (protecting against single data centre failure) with cross-region backup to AWS eu-west-1 (Ireland) for catastrophic regional failure. RTO: from 48-72 hours to 1 hour (automated failover within the Stockholm region). RPO: from 24 hours to 15 minutes (continuous replication). Backup: automated daily snapshots of all systems — retained for 30 days. Database: point-in-time recovery enabled — database restorable to any point in the last 35 days. DR testing: quarterly DR drills — automated failover tested and verified. The improvement: from "hope we can restore from tape" to "tested and automated recovery in under an hour." (5) Factory connectivity: reliable production connections. AWS Direct Connect: dedicated 1Gbps connection from Helsinki to AWS Stockholm — reliable, low-latency connectivity for production-critical applications. Factory VPN: upgraded VPN connections from Tampere and Oulu factories — redundant tunnels with automatic failover. MES integration: factory MES systems accessing cloud-hosted applications with <15ms latency — production operations unaffected by the migration. Edge computing: AWS IoT Greengrass deployed at factories — local processing for latency-sensitive factory operations with cloud synchronisation.
Results over 10 months. Infrastructure cost: annual infrastructure cost from €380,000 (colocation + hardware amortisation + licensing) to €185,000 (AWS + GCP) — 51% reduction. The saving: eliminating colocation fees (€95,000/year), hardware replacement costs, and reducing licensing costs (Windows Server, VMware — replaced by cloud services). 3-year saving: €585,000 (compared to the €480,000 hardware refresh option that would have maintained status quo costs). IT productivity: IT team time on infrastructure maintenance from 70% to 20%. The 50% freed time: redirected to business projects — factory digitalisation, customer portal enhancement, and data analytics. IT capability: the team developing cloud skills (AWS certifications) — becoming more valuable to the business. No additional IT staff hired despite business growth. Application performance: SAP month-end reporting from 45 minutes to 3 minutes (93% improvement). SAP inventory queries from 20 seconds to 1.5 seconds. CRM response time: from 2-3 seconds (on ageing hardware) to <0.5 seconds (on cloud). User satisfaction: internal user satisfaction with IT systems from 2.8/5 to 4.3/5 (54% improvement). Munich sales team: CRM performance improvement making them measurably more productive — 15% more customer interactions per day. Disaster recovery: RTO from 48-72 hours to <1 hour. RPO from 24 hours to 15 minutes. DR confidence: quarterly testing demonstrating reliable recovery — the CFO describing the improvement as "the difference between hoping for the best and knowing we'll be fine." Zero unplanned downtime in 10 months (from 3 infrastructure-related outages in the 6 months before migration). Availability: 99.98% (exceeding the company's 99.9% target). Multi-site performance: factory latency from 200-400ms to 8-15ms. The improvement: factory MES and quality systems performing as if locally hosted — production operations smoother and faster. Stockholm and Munich: both offices experiencing near-local application performance. Migration cost: €125,000 (10-week project — assessment, migration, SAP migration, DR setup, and factory connectivity). Monthly cloud cost: €15,400 (AWS + GCP). Annual value: €195,000 (infrastructure saving) + IT productivity (equivalent of 1.5 additional FTEs — €90,000) + performance improvement (user productivity) + DR improvement (risk reduction). Total annual value: €285,000+. ROI: 2.3x in the first year on migration investment (improving in subsequent years as cloud costs optimise further).
Migrate from on-premise or legacy hosting to the cloud with zero downtime and minimal disruption.
Build applications that fully leverage cloud services — serverless, managed databases, and auto-scaling.
Avoid vendor lock-in with architectures that work across AWS, GCP, and Azure.
Audit and optimize your cloud spend. Reserved instances, spot pricing, and right-sizing to cut costs by 30-50%.
IAM policies, encryption, VPCs, and compliance frameworks to protect your cloud infrastructure.
24/7 monitoring, maintenance, and optimization of your cloud environment so you can focus on your product.
Helsinki's cloud market includes Finnish IT companies (Tietoevry, Digia, Nordcloud — established Finnish cloud providers and system integrators. Strong Finnish market presence at €150-250/hour), hyperscaler partners (AWS, Azure, GCP partner network — certified partners implementing cloud solutions. Platform expertise but varying depth of Finnish business understanding), managed service providers (Nordic MSPs — cloud management and operations. Operational focus with less strategic cloud architecture capability), and internal IT (Finnish companies managing cloud internally — growing but often struggling with multi-cloud complexity and 24/7 operations). ZTABS provides cloud services with Finnish business context — Nordic system integration (Netvisor, Procountor, Finnish banking), Finnish data residency expertise (GCP Hamina, Finnish cloud options), and practical cloud architecture that balances Finnish compliance requirements with cloud innovation.
Cloud services in Helsinki range from €30,000-80,000 for focused migration (10-30 VMs, standard applications, 6-8 weeks) to €80,000-250,000 for comprehensive migration (50+ VMs, SAP, multi-site, DR, 8-14 weeks). Managed services: €2,000-8,000/month (monitoring, backup, patching, and support). Cloud infrastructure: additional (varies by workload). ZTABS provides fixed-price migration with cloud cost guarantees for the first year.
Verified reviews from real client engagements — sourced from our public testimonial archive and Clutch profile.
My experience is throughout positive. Communication, service, the short response times and the flawless execution of a challenging topic was absolutely great. ZTABS is definitely my first choice again.
Christian Neff
Bank Software Advisory · Bank Software Advisory
Fintech
Fantastic Agency! I couldn't fault them even if I tried. They always go above and beyond to meet your expectations and always produces quality work. Thank you ZTABS.
Stephanie Kal
CEO · Beauty Finder Australia
Marketplace
It has been great working with ZTABS. They bounce off the ideas along the way. Amazing Experience.
Joel Rowe
CEO · Drill Quoter
Marketplace
We don't just contract — we ship and operate our own software. 17 products in production.
Common questions about cloud for Helsinki businesses
Depends on requirements. AWS (Stockholm): broadest services, strong enterprise capability. Azure: best for Microsoft-heavy organisations (M365, Teams, Dynamics). GCP (Hamina, Finland): Finnish data residency and strong analytics/AI. We assess your specific needs — technology stack, data residency, and workload characteristics — and recommend accordingly.
ZTABS is a remote-first cloud agency serving Houston businesses — including cloud migration, cloud-native development, multi-cloud strategy. We work with Energy & Oil/Gas, Healthcare & Biotech, Aerospace & Defense companies in Houston, TX via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Cloud in New York, NYZTABS is a remote-first cloud agency serving New York businesses — including cloud migration, cloud-native development, multi-cloud strategy. We work with Finance & Fintech, Media & Advertising, Fashion & Retail companies in New York, NY via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Cloud in Los Angeles, CAZTABS is a remote-first cloud agency serving Los Angeles businesses — including cloud migration, cloud-native development, multi-cloud strategy. We work with Entertainment & Media, E-commerce & DTC Brands, Gaming & AR/VR companies in Los Angeles, CA via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Web Development in Helsinki, FinlandZTABS is a remote-first web development agency serving Helsinki businesses — including full-stack development, progressive web apps, api development. We work with Gaming, AI & Deep Tech, CleanTech companies in Helsinki, Finland via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Web Design in Helsinki, FinlandZTABS is a remote-first web design agency serving Helsinki businesses — including ui/ux design, responsive design, custom interfaces. We work with Gaming, AI & Deep Tech, CleanTech companies in Helsinki, Finland via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
AI Development in Helsinki, FinlandZTABS is a remote-first AI development agency serving Helsinki businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with Gaming, AI & Deep Tech, CleanTech companies in Helsinki, Finland via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Cloud ServicesLearn more about our cloud services nationwide.
Partner with ZTABS for expert cloud in Helsinki. Get a free consultation today.
