Spryker Pricing in 2026: How Much Does Spryker Really Cost

You're researching Spryker pricing and hitting the same wall everyone hits — there's no pricing page. No tiers. No "starting at" number. Just a "Contact Sales" button and the sinking feeling that if you have to ask, it's expensive.

You're right. Third-party sources have described Spryker pricing as developer-seat based, but Spryker does not publicly document a current standard pricing model. Public review sites like Capterra and SoftwareSuggest list no verified starting price, showing only "Contact vendor for pricing." Total costs climb significantly once you factor in implementation, partner fees, developer onboarding, and ongoing maintenance. For mid-to-large B2B deployments, total first-year costs routinely reach six and seven figures when all cost layers are included.

This guide breaks down every cost layer so you can build an accurate Spryker budget — no sales call required.

Key Takeaways

• Third-party sources have historically described Spryker as using per-developer seat licensing, though Spryker does not publicly confirm its current pricing model. Costs are custom-quoted through direct sales or AWS Marketplace
• Spryker does not publish base licensing prices; all pricing requires direct engagement with their sales team or a certified partner
• Implementation costs for mid-to-large B2B deployments range from $200,000 to $500,000+ according to generic enterprise ecommerce analysis, often matching or exceeding the first year's license fee
• Multiple user reviews cite a steep learning curve and high setup complexity, adding substantial hidden labor costs
• Spryker was classified as a Visionary in the 2025 Gartner Magic Quadrant, down from Leader in 2024

Why Teams Are Questioning Spryker Pricing in 2026

Three trends are pushing enterprise commerce teams to scrutinize Spryker's cost structure more carefully than in previous years:

Engineering budgets are tightening. After years of aggressive hiring, most tech organizations entered 2026 with leaner engineering teams and stricter per-head cost justification. If Spryker's licensing model is indeed tied to developer seats as third-party sources have described, every new hire could increase the platform bill, creating friction between growth plans and cost control.

Composable commerce alternatives have matured. When Spryker launched its composable approach, few platforms offered comparable modularity. In 2026, composable commerce has expanded rapidly — one market-research firm estimated the broader composable applications market at $7.55 billion in 2025 — with multiple API-first platforms offering similar flexibility at lower total cost of ownership and without requiring specialized PHP/Symfony expertise.

The Gartner downgrade raised questions. Spryker's shift from Leader to Visionary in the 2025 Gartner Magic Quadrant prompted enterprise procurement teams to re-evaluate their platform shortlists. While the platform's capabilities remain strong for B2B, the reclassification has added a new variable to multi-year commitment decisions.

Why Spryker Pricing Is So Hard to Research

Three factors make Spryker one of the most opaque platforms to price out before a sales call:

No public pricing page. Unlike most enterprise commerce platforms that publish at least a starting price or tier structure, Spryker doesn't list any pricing on its website. The only path to a quote is through their sales team or a certified implementation partner.

Per-developer seat licensing is unusual. Most enterprise ecommerce platforms price based on GMV, revenue tiers, or flat annual licensing. Third-party sources have described Spryker's model as per-developer, meaning your cost may be directly tied to engineering headcount — a variable most procurement teams don't use for software budgeting. This makes apples-to-apples comparisons with other platforms nearly impossible without detailed scoping.

Module selection creates infinite pricing permutations. With hundreds of modules, the number of possible configurations is enormous. A B2C catalog with basic checkout costs fundamentally different from a B2B marketplace with CPQ, approval workflows, and customer-specific pricing. Spryker can't publish a simple pricing table because no two deployments look alike.

This opacity isn't accidental — it's a common enterprise sales strategy. But it creates real friction for technical leaders trying to build accurate budgets before committing to a vendor evaluation cycle.

Spryker Pricing Model Explained

Spryker's pricing model differs fundamentally from most ecommerce platforms. While Shopify Plus charges based on revenue tiers and Adobe Commerce uses annual licenses tied to GMV, third-party sources have described Spryker as pricing primarily based on the number of developer seats your team requires, though Spryker does not publicly document this model.

If accurate, this per-developer approach means a five-person dev team pays significantly less than a twenty-person team — regardless of how much revenue the platform generates. For organizations planning to scale their engineering departments, this could introduce cost unpredictability that revenue-based licensing avoids.

Per-Developer Seat Licensing

According to user reports on G2 and industry analysis, Spryker's core licensing fee may be determined by how many developers need platform access. The reported per-seat model works as follows:

• Base subscription covers platform access, cloud hosting via Spryker Cloud Commerce OS on AWS, and standard support
• Additional seats increase the monthly or annual commitment proportionally
• Module selection further adjusts pricing — Spryker offers hundreds of modules, and you pay for the capabilities you activate

One TrustRadius reviewer noted: "Without any developing experience, Spryker Cloud Commerce OS could be too expensive." The platform's value proposition depends heavily on having skilled developers who can fully leverage its modular architecture.

Module-Based Configuration

Spryker's extensive module library is both its greatest strength and a pricing variable most buyers underestimate. Rather than purchasing a monolithic platform with every feature included, you select the modules your business needs: B2B order management, marketplace functionality, customer-specific pricing, approval workflows, and more.

This composable approach means you avoid paying for unused features. However, it also means the final license cost varies dramatically between a B2C retailer needing basic catalog and checkout versus a B2B manufacturer requiring CPQ, multi-warehouse inventory, and approval chains.

To illustrate the module complexity: Spryker's B2B suite alone includes company accounts with approval workflows, customer-specific pricing and catalogs, quote-to-cash and CPQ support, measuring and packing units, multiple wishlists and carts, PO payment options, and role-based permissions. Its marketplace module adds multi-vendor support that unifies B2B, B2C, and third-party seller models on one platform.

Each of these modules carries a Spryker pricing implication, and most organizations don't realize the full module bill until they're deep into scoping.

Support and Service Tiers

Spryker offers tiered support packages that layer onto the base licensing cost:

• Standard support is typically included in the base license
• Premium support with faster SLA response times and dedicated account management adds additional cost to the annual license fee, though the exact premium is not publicly documented
• Professional services for architecture reviews, performance optimization, and custom development are quoted separately

According to one anecdotal TrustRadius user review, the license cost is "a lot less than SAP Commerce Cloud and Intershop." While this suggests Spryker may sit in the mid-to-upper range of enterprise commerce platforms rather than at the absolute top, a single user review is not sufficient to verify market positioning.

What Spryker Implementation Really Costs

The license fee is only the starting point. For most organizations, implementation represents the single largest component of Spryker pricing — and the number most sales conversations underemphasize.

Professional Services and Partner Fees

Spryker implementations typically require a certified implementation partner. Industry analysis from Centarro estimates that generic enterprise ecommerce implementations for mid-to-large B2B deployments cost $200,000 to $500,000+, while complex enterprise deployments can exceed $1 million. Note that these figures represent enterprise ecommerce platforms generally, not Spryker-specific pricing.

These costs cover:

• Discovery and architecture planning — business requirements analysis over several weeks
• Core platform configuration — module selection, data model design, workflow setup
• Custom development — building features not available out-of-the-box
• Third-party integrations — ERP, PIM, CRM, payment gateway, and shipping connections
• Data migration — transferring product catalogs, customer records, and order history
• Quality assurance and testing — end-to-end testing across all configured modules

Notable Spryker implementation partners include Valantic, which built Daimler Truck's B2B spare parts marketplace.

Implementation timelines vary widely. Spryker's own customer stories page advertises sub-3-month time-to-market, while G2 user data shows an average reported implementation time of approximately 9 months. During this period, your team will be running parallel systems — the legacy platform stays live while Spryker is built out, tested, and migrated. This dual-operation cost is easy to underestimate: you're paying for both platforms, both dev teams, and the project management overhead to coordinate the transition. As one G2 reviewer described the architecture, Spryker's headless, decoupled approach serves as a "North Star for global operations" — but reaching that north star takes significant upfront investment.

Developer Onboarding and Training

Spryker's proprietary PHP stack — built on Symfony with a Yves (frontend) and Zed (backend) architecture — requires specialized knowledge that general PHP developers don't possess out of the box.

Based on G2 user reviews and industry reports, multiple reviewers cite a steep learning curve and high setup complexity. Senior developers with relevant Symfony experience ramp up faster, while junior developers face a significantly longer path to full productivity. The exact timelines vary based on experience level, team support structures, and project complexity.

During this ramp-up period, developers work at reduced efficiency — writing less code, requiring more oversight, and producing more bugs. For a team of five developers, even a moderate productivity gap represents significant sub-optimal labor costs.

This is one of the most frequently cited drawbacks in user reviews: "Spryker offers great flexibility, scalability, and customization, but comes with a steep learning curve that can slow down initial development" (G2).

5 Hidden Spryker Pricing Costs You Should Know Before Signing

Beyond the license and implementation, five Spryker pricing categories catch most buyers off guard:

1. Missing out-of-the-box features. Despite hundreds of modules, many standard ecommerce features require custom development. One G2 reviewer stated: "In some parts Spryker is very good, but in comparison to other major ecommerce platforms there are many basic ecom features that are not there out of the box." Budget accordingly for custom development to fill functional gaps, as costs will vary significantly based on scope.
2. Per-seat scaling surprises. If the per-developer licensing model applies, as third-party sources have described, then as your team grows from five to fifteen developers, licensing costs can multiply — even if revenue stays flat. Unlike revenue-based models where costs scale with business success, a per-developer model penalizes growth in engineering capacity.
3. Specialized talent premiums. Spryker developers are harder to hire than general PHP or JavaScript developers. The Yves/Zed architecture knowledge base is smaller, which means you'll likely pay above-market salaries or invest heavily in training.
4. Ongoing maintenance complexity. Spryker's modular architecture requires more hands-on maintenance than SaaS platforms. Module updates, version compatibility checks, and infrastructure monitoring require dedicated DevOps resources. Reviews on G2 describe maintenance effort as "resource-intensive."
5. Migration and replatforming costs. Migrating from Magento, SAP, or another legacy platform adds significant data migration costs depending on catalog complexity and integration depth. The implementation timeline also means months of running two platforms simultaneously.

Spryker Total Cost of Ownership by Business Size

Spryker pricing depends on team size, business complexity, and module activation. The following is an illustrative estimate of TCO for three common deployment scenarios. These figures are not independently verified and should be treated as internal modeling assumptions, not factual market benchmarks:

These estimates include fully loaded developer costs because Spryker is not a platform you can run without dedicated technical staff. If you're comparing Spryker against platforms that require fewer or no dedicated developers, factor the full labor cost into your comparison.

Year 2 and beyond: After the implementation year, ongoing costs drop significantly since you've already absorbed the implementation and onboarding expenses. For a mid-market deployment, estimated Year 2+ annual costs fall in the range of $1.38–$2.17 million (licensing + salaries + maintenance). The ROI inflection point — where Spryker's power starts justifying its cost — may arrive 18–24 months after go-live, once the team is fully productive and the platform handles enough transaction volume to offset the investment. However, these timelines are modeled estimates, not verified benchmarks.

Spryker pricing for B2B vs. B2C vs. marketplace: B2B implementations are generally the most expensive due to CPQ, approval workflow, and customer-specific pricing modules. B2C deployments can be leaner if catalog complexity is lower. Marketplace builds carry the highest implementation costs because they require vendor onboarding workflows, commission management, and split-payment infrastructure on top of the core commerce modules.

Important note: Spryker pricing is not published officially. These ranges are illustrative estimates informed by G2 user reviews, Centarro's generic enterprise ecommerce analysis, and user-reported data on TrustRadius. Note that Capterra currently shows zero user reviews for Spryker, and SoftwareSuggest lists no verified pricing. Your actual costs may differ based on negotiated terms, module selection, and regional partner rates.

What Spryker Enterprise Buyers Should Expect

For organizations evaluating Spryker pricing at the enterprise level, several additional cost and value factors apply.

Spryker announced a new financing round in December 2025 led by TCV and One Peak. The official announcement did not disclose the round amount or cumulative total funding, though external aggregators like GetLatka estimate total funding at approximately $152 million. This signals financial stability and continued product investment — an important consideration for enterprise buyers committing to multi-year contracts.

The platform earned 2025 Ecommerce Solution of the Year from RetailTech Breakthrough. Separately, Spryker was ranked #1 for B2B Digital Commerce in Gartner's 2024 Critical Capabilities report, though the 2025 Critical Capabilities placed it at #2 in that category. Its Gartner Magic Quadrant position also shifted from Leader in 2024 to Visionary in 2025 — a change enterprise procurement teams should factor into vendor evaluations.

Enterprise deals with Spryker typically include:

• Multi-year contract discounts — committing to 2–3 years can reduce annual licensing by 10–20%
• Dedicated customer success manager — assigned to accounts above certain spending thresholds
• SLA guarantees — uptime commitments and response time guarantees for mission-critical commerce
• Co-development opportunities — for strategic accounts, Spryker may invest in building features that benefit both parties

Notable enterprise customers include ALDI, Siemens Healthineers, Ricoh, and Daimler Truck. Daimler Truck's B2B spare parts marketplace, built with partner Valantic, demonstrates the platform's strength in complex B2B scenarios requiring customer-specific pricing, real-time inventory visibility, and multi-region deployment. As Robert Bruce, CIO of Daimler Truck Overseas, stated: "With Spryker, we combined customer-specific pricing, real-time inventory visibility, and a scalable marketplace architecture into one foundation."

Spryker also recently introduced AI capabilities, including a model-agnostic AI foundation and agentic AI for complex B2B processes. For enterprises evaluating long-term platform viability, external aggregator GetLatka estimates 2024 revenue at $26.2 million — though this is not an official company disclosure. The company's 150+ global customers, confirmed by official Spryker materials, indicate a growing but still mid-market vendor — important context when committing to a multi-year platform partnership.

Spryker Pros and Cons: 2026 Assessment

G2 Rating: 4.4/5 (140 reviews, 97% four or five stars)

Pros

• Unmatched B2B flexibility — approval workflows, customer-specific pricing, and CPQ capabilities that most platforms require third-party apps or heavy customization to achieve
• True composable architecture — hundreds of modules let you build exactly what you need without paying for features you won't use
• Native marketplace support — unified B2B, B2C, and third-party seller models on a single platform, eliminating the need for separate marketplace software
• Lower licensing than SAP/Intershop — user reviews on TrustRadius suggest Spryker's license fees undercut the biggest enterprise incumbents, though this is anecdotal
• Strong enterprise customer proof — ALDI, Siemens Healthineers, Daimler Truck, and Ricoh validate the platform's ability to handle global-scale commerce
• Cloud-native on AWS — fully managed Spryker Cloud Commerce OS eliminates infrastructure management overhead

Cons

• No public pricing — the opaque quoting process makes budget planning difficult before sales engagement
• Steep learning curve — multiple reviews cite extended ramp-up periods for developers to reach full productivity on the Yves/Zed architecture
• Per-developer seat licensing (reported) — if accurate, costs scale with engineering headcount, not business success, penalizing companies that need to grow their dev teams
• Missing out-of-the-box features — despite hundreds of modules, many standard ecommerce capabilities still require custom development
• Implementation partner dependency — most deployments require expensive certified partners
• Small talent pool — Spryker's proprietary PHP stack limits hiring options and commands salary premiums over general ecommerce developers
• Gartner downgrade — moved from Leader to Visionary in the 2025 Magic Quadrant, raising questions about long-term product trajectory

Best For

Large enterprises (200+ employees) running complex B2B commerce with approval workflows, customer-specific pricing, multi-vendor marketplace needs, and the budget to invest significantly in Year 1 implementation alongside substantial annual licensing. Not suitable for companies without dedicated development teams or annual commerce budgets under $500,000.

Who Should (and Shouldn't) Pay for Spryker

Spryker delivers clear value for a specific buyer profile — and creates unnecessary cost burden for everyone else.

Spryker is worth the investment if you:

• Operate complex B2B commerce with approval workflows, customer-specific pricing, and CPQ requirements
• Need native marketplace capabilities to unify B2B, B2C, and third-party seller models on one platform
• Have or plan to build a dedicated development team of 5+ Spryker-skilled engineers
• Process enough volume that a six-figure platform investment represents less than 1–2% of annual digital revenue
• Require multi-store capabilities for global subsidiaries with localized catalogs and storefronts

Spryker is not the right investment if you:

• Have an annual digital commerce budget under $500,000
• Need to launch in under three months
• Don't have in-house developers or a committed agency partnership
• Run primarily B2C with straightforward catalog and checkout needs
• Want subscription commerce as a core feature without significant custom development

As G2 reviewers consistently note, the platform is "not suitable for small or budget-conscious businesses." Spryker rates 4.4 out of 5 on G2 across 140 reviews, with 97% of reviewers giving four or five stars — but that satisfaction comes from enterprises with the budget and team to leverage it fully.

Signs You May Have Outgrown Spryker

Even organizations that initially chose Spryker for the right reasons may hit limitations that signal it's time to re-evaluate:

• Developer costs consume more than 40% of your commerce technology budget and the per-seat model (if applicable) accelerates that ratio as you hire
• Basic feature requests consistently require custom module development because out-of-the-box capabilities don't cover your evolving use cases
• Non-technical team members can't self-serve — marketing, merchandising, and operations rely entirely on developers for routine changes
• Subscription or recurring revenue models are becoming core to your business, but the platform requires significant custom work to support them
• Time-to-market for new storefronts or regions exceeds three months when competitors are launching in weeks
• Maintenance overhead is growing — module updates, compatibility testing, and infrastructure management consume an increasing share of developer capacity

These pain points don't necessarily mean Spryker was the wrong choice initially. Business requirements evolve, and platforms that served complex B2B needs well may become a drag as companies shift toward faster iteration cycles, subscription models, or composable architectures that require fewer specialized developers.

How to Reduce Your Spryker Costs

If you're already on Spryker or committed to the platform, several strategies can reduce your Spryker pricing burden:

1. Audit your module usage. Spryker's extensive module library means you may be paying for activated modules you don't use. Conduct a quarterly module audit and deactivate capabilities that aren't serving active business processes. Even small reductions compound over a multi-year contract.

2. Negotiate multi-year contracts. Spryker offers discounts for longer commitments. Locking in a 2–3 year term can save 10–20% on annual licensing. Time this negotiation around contract renewal when you have the most leverage.

3. Invest in internal training over external consultants. The steep onboarding curve is expensive, but it's cheaper long-term than perpetual reliance on implementation partners. Build an internal Spryker center of excellence with structured training programs.

4. Explore AWS Marketplace purchasing. Spryker is available on AWS Marketplace. While some organizations may be able to leverage existing AWS agreements, the specifics of committed spend credit applicability are not publicly confirmed for Spryker. Contact AWS or Spryker directly for details.

5. Right-size your developer seats. Not every team member who touches the commerce stack needs a full developer seat. Identify which roles truly need platform access versus those who can work through APIs, the admin interface, or storefront tools.

6. Consolidate multi-store deployments. Spryker's multi-store capabilities allow multiple storefronts to run on a single instance. If you're running separate environments for different regions or brands, consolidating to multi-store can reduce infrastructure and licensing costs. According to user reports, multi-store on Spryker is "almost just configuration to onboard subsidiaries with their own catalog and storefront" — one of the platform's stronger cost-efficiency features.

7. Phase your module rollout. Rather than activating every module at launch, start with core commerce capabilities and add B2B, marketplace, or advanced modules in later phases. This spreads implementation costs across multiple budget cycles and lets your team build Spryker expertise incrementally before tackling complex configurations.

The most effective Spryker pricing strategy is simple but often overlooked: right-size the platform to your actual needs before signing. Many organizations over-scope their initial deployment, activating modules and hiring developers for capabilities they won't use in Year 1. A focused Phase 1 with core features — followed by iterative expansion — consistently delivers better TCO outcomes than trying to build the complete vision upfront.

Final Verdict: Is Spryker Worth the Investment in 2026?

Spryker delivers genuine value for large enterprises running complex B2B commerce — approval chains, customer-specific pricing, multi-vendor marketplaces, and global multi-store operations. Its modular, MACH-aligned architecture provides flexibility that monolithic platforms can't match, and its enterprise customer base (ALDI, Siemens Healthineers, Daimler Truck) proves it handles serious scale.

But that value comes at a serious cost. Between custom licensing, six-figure implementation fees, specialized developer salaries, and a steep onboarding curve, Spryker's total cost of ownership starts in the hundreds of thousands and scales into the millions for enterprise deployments. For organizations without dedicated development teams and enterprise-level budgets, the platform creates more financial burden than business value.

If you're evaluating Spryker and finding the cost and complexity difficult to justify, Swell delivers API-first commerce architecture with native subscription management, unlimited product variants, custom data models, and multi-currency support across 230 currencies — without per-developer seat licensing or six-figure implementation timelines.

See Pricing →

Frequently Asked Questions

How much does Spryker cost per month?

Spryker doesn't publish fixed monthly pricing. Public review sites like Capterra and SoftwareSuggest list only "Contact vendor for pricing" with no verified starting price. Enterprise deployments typically involve six-figure annual commitments. The actual cost depends on your negotiated terms, selected modules, and support tier.

Is Spryker expensive for small businesses?

Yes. Spryker is designed for mid-to-large enterprises and is not suitable for small businesses. Between licensing, implementation (estimated at $200,000–$500,000+ for generic enterprise ecommerce platforms according to Centarro), and the specialized developers required to run it, total first-year costs for even the smallest deployments start at several hundred thousand dollars.

What is Spryker's pricing model?

Third-party sources have described Spryker as using per-developer seat licensing, where your cost scales with the number of developers who access the platform, not with your revenue or transaction volume. However, Spryker does not publicly document its current pricing model. This is fundamentally different from revenue-tiered models used by platforms like Adobe Commerce or Shopify Plus.

What are the hidden costs of Spryker?

The five most common hidden costs are: (1) custom development for missing out-of-the-box features, (2) potential per-seat cost scaling as your dev team grows, (3) salary premiums for specialized Spryker developers, (4) ongoing maintenance complexity requiring dedicated DevOps, and (5) data migration costs from legacy platforms.

What is the total cost of ownership for Spryker?

For a mid-market B2B deployment with 8–12 developers, illustrative first-year TCO estimates range from $1.78 million to $2.85 million when factoring in licensing, implementation, developer salaries, onboarding productivity loss, and ongoing maintenance. Enterprise deployments with 15–25+ developers may exceed $5 million in the first year. These are modeled estimates, not verified benchmarks.

How long does Spryker implementation take?

Implementation timelines vary widely. Spryker's own marketing claims sub-3-month time-to-market, while G2 user data shows an average reported implementation time of approximately 9 months. Timelines depend on deployment complexity, including discovery, platform configuration, custom development, third-party integrations, data migration, and testing phases.

Does Spryker offer a free trial?

Spryker does not offer a self-service free trial. The platform follows a traditional enterprise sales process — you'll need to contact their sales team for a demo and custom quote. Spryker is also available on AWS Marketplace, and the AWS Marketplace license agreement references a 45-day evaluation period for evaluation software, though this is not the same as a public self-serve free trial.

What companies use Spryker?

Notable Spryker customers include ALDI, Siemens Healthineers, Ricoh, Daimler Truck, ZF, Hilti, Scania, and International Motors. The platform serves 150+ customers globally, primarily in B2B manufacturing, distribution, and enterprise retail.

How does Spryker compare to other enterprise platforms on cost?

One anecdotal TrustRadius user review describes Spryker's licensing as less expensive than SAP Commerce Cloud and Intershop. Generic enterprise ecommerce implementation costs fall in the $200,000–$1,000,000+ range according to Centarro. The reported per-developer seat model is unique among major platforms — most competitors use revenue-based or GMV-based pricing instead.

Is Spryker's Gartner recognition worth paying a premium for?

Spryker was classified as a Visionary in the 2025 Gartner Magic Quadrant, down from Leader in 2024. While Gartner recognition validates the platform's capabilities — particularly for complex B2B and marketplace use cases — the shift from Leader to Visionary suggests enterprise buyers should evaluate whether Spryker's product trajectory aligns with their long-term needs before committing to multi-year contracts.

Should I budget for a Spryker proof of concept before committing?

Given Spryker's complexity and cost, running a proof of concept (POC) is standard practice for enterprise evaluations. Budget and timeline for a POC will vary based on scope and the implementation partner selected. A POC lets your team validate that Spryker's modular architecture handles your specific use cases — approval workflows, custom pricing rules, marketplace logic — before committing to a full-scale implementation. Many enterprise buyers skip this step and regret it when they discover functional gaps during full deployment.

Can a small team run Spryker without an implementation partner?

Realistically, no. Spryker's Yves/Zed architecture, module configuration system, and deployment pipeline require specialized expertise that general PHP developers don't have. While technically possible for a senior Symfony team to self-implement, user reviews consistently describe the learning curve as steep even for experienced developers. Without partner support, you risk extended timelines, architectural mistakes, and higher long-term costs from technical debt. Budget for at least initial partner engagement even if you plan to bring maintenance in-house later.