Agentic AI is growing faster than almost any enterprise technology in recent memory, and deploying into production more slowly than almost any other. The global market hit $7.29 billion in 2025 and is projected to reach $139.19 billion by 2034. But only 23% of organizations have actually scaled an agentic AI system in production, even as over 40% of current projects are forecast to be canceled by 2027.

The numbers below capture both sides of that gap: the scale of investment and intent, and the harder reality of governance, security, and organizational readiness that determines who actually gets there.

Top agentic AI statistics for 2026

Here are the key numbers shaping agentic AI in 2026:

1. The global agentic AI market is projected to grow from $9.14 billion in 2026 to $139.19 billion by 2034, at a compound annual growth rate (CAGR) of 40.5%.
2. 40% of enterprise applications will feature task-specific AI agents by the end of 2026, up from less than 5% in 2025, a roughly eightfold increase in a single year.
3. Only 23% of organizations report scaling an agentic AI system in production, and a further 39% are still experimenting.
4. Over 40% of agentic AI projects are projected to be canceled by the end of 2027, largely due to escalating costs, unclear business value, and inadequate risk controls.
5. 82% of organizations already use AI agents, but only 44% have security policies in place to govern them.
6. 80% of companies report their AI agents have already taken unintended actions, including accessing unauthorized systems and sharing sensitive data without authorization.
7. 68% of all customer service and support interactions with technology vendors will be handled by agentic AI by 2028, with 56% of organizations expecting to handle half the interactions within 12 months.
8. By 2029, more than one billion AI agents are expected to be in use worldwide, roughly 40 times the number active in 2025.
9. Hermes Agent surpassed OpenClaw as the most-used AI agent on OpenRouter’s global daily rankings on May 10, 2026, processing 224 billion tokens per day against OpenClaw’s 186 billion.
10. AI spending globally is projected to grow 31.9% year-over-year between 2025 and 2029, reaching $1.3 trillion and exceeding 26% of all worldwide IT spending, growth driven heavily by agentic AI applications.

Agentic AI market size

The market size estimates for agentic AI vary significantly across research firms because they define the category differently. Some count only autonomous task-completion systems, while others include any AI with planning or tool-use capabilities. 

The figures below reflect the most widely cited projections from primary sources, with Fortune Business Insights as the anchor.

• $7.29 billion global agentic AI market valuation in 2025, projected to grow to $9.14 billion in 2026 and $139.19 billion by 2034, at a 40.5% CAGR. North America held 33.6% market share in 2025, valued at $2.45 billion (Fortune Business Insights).
• 31.9% year-over-year AI spending growth projected between 2025 and 2029, reaching $1.3 trillion by 2029 and exceeding 26% of all worldwide IT spending, driven by agentic AI-enabled applications (IDC).
• Approximately $450 billion is the best-case estimate for agentic AI’s contribution to enterprise application software revenue by 2035, representing approximately 30% of all enterprise software revenue, up from 2% in 2025 (Gartner).
• 34.19% market share is held by the machine learning segment in agentic AI technology in 2026, while the deep learning segment is expected to grow fastest, enabling autonomous decision-making and generative AI capabilities (Fortune Business Insights).
• 32.2% is the projected application share for customer service and virtual assistants in the agentic AI market in 2025, the largest of any use case, driven by demand for instant, personalized, high-volume support (Fortune Business Insights).

Low-code development is accelerating in parallel, with four in five companies now treating it as strategically important, a shift that’s making AI-native tooling accessible to organizations without large engineering teams.

Enterprise adoption of agentic AI

The headline number from Gartner – 40% of enterprise applications integrating task-specific AI agents by the end of 2026 – points to one of the fastest technology integration shifts in enterprise history, up from less than 5% in 2025. But adoption data from McKinsey tells a more grounded story: 

• 23% of organizations have actually scaled an agentic AI system into production, while a further 39% are experimenting and 62% are engaged in some form. The remaining third has not yet begun.
• 88% of organizations report regular AI use in at least one business function, up from 78% the previous year, reflecting broader enterprise AI adoption trends over the past two years.

The interest-to-production gap shows up consistently across surveys. In the US specifically, large-company executives are among the most bullish: 93% of US IT executives at companies with over $1 billion in revenue are extremely or very interested in exploring agentic AI, and 37% say they are already using it. 

At the same time, 90% say their business processes would be improved by agentic AI, but security vulnerabilities (56%) and high implementation costs (37%) top the list of concerns.

• In the US specifically, 79% of US companies are already adopting AI agents, and 88% plan to increase AI-related budgets in the next 12 months due to agentic AI, yet only 45% are fundamentally rethinking operating models and only 42% are redesigning processes around agents (PwC AI Agent Survey).

• 66% of companies adopting AI agents report measurable productivity gains, 57% report cost savings, and 55% faster decision-making. Trust drops sharply for high-stakes tasks, with only 20% of executives trusting agents with financial transactions versus 38% for data analysis (PwC AI Agent Survey).
• 55% of businesses are actively developing or deploying an agentic AI operating model, 82% of C-suite executives say functional silos actively block value, and 75% say agentic AI will significantly redefine their global service delivery model by the end of 2026 (IBM Blueprint for Agentic Operations).

A separate IBM survey of C-suite executives captures a recurring pattern: 78% say achieving maximum benefit from agentic AI requires a new operating model, yet 78% of AI investment has so far gone into optimizing what already exists.

The IBM Agentic AI’s Strategic Ascent finds that AI investment is concentrated on improving existing processes rather than building new capabilities.

Today, 24% of executives say AI agents take independent action in their organization. By 2027, 67% expect that to be the case, with autonomous decision-making in workflows growing from 28% today to 57%.

• Companies that excel in integrating cybersecurity, embedding ethics analysis, and implementing workflow-specific language models are 32 times more likely to achieve top-tier business performance than those with minimal implementation. This group represents 17% of the survey sample and expects 41% productivity gains versus 31% for all others (IBM Agentic AI’s Strategic Ascent).
• Over 40% of agentic AI projects will be canceled by the end of 2027 due to escalating costs, unclear business value, and inadequate risk controls. Gartner estimates only about 130 of the thousands of vendors claiming to offer agentic AI are actually delivering it, with the rest engaged in what Gartner terms “agentwashing” (Gartner).
• At least 15% of day-to-day work decisions will be made autonomously through agentic AI by 2028, up from 0% in 2024. By the same year, 33% of enterprise software applications will include agentic AI, up from less than 1% in 2024 (Gartner).

The data describes an enterprise landscape where adoption is broad at the level of intent but narrow at the level of production. The organizations pulling ahead are not necessarily the ones with the largest AI budgets. They are the ones treating governance and operating model design as foundational work rather than a follow-on step.

Expert tip

The gap between exploring agentic AI and running it in production comes down to a few unglamorous factors: data quality, integration readiness, and governance maturity. Organizations that invest in these foundations before deploying agents are the ones scaling successfully, and their returns justify the groundwork. Those who skip this step tend to become the cautionary data points.

Tomas Rasymas

Head of AI at Hostinger

Agentic AI use cases by industry

The pattern holds across sectors, though where agentic AI lands first depends on which tasks are high-volume, structured, and costly enough to justify autonomous action.

Customer service

Customer service has the largest application share in the agentic AI market and the clearest deployment timeline from analysts. Agentic AI in this context means systems that handle queries end-to-end, retrieving account data, resolving disputes, and processing requests, without escalating to a human agent.

• Agentic AI will autonomously resolve 80% of common customer service issues without human intervention by 2029, reducing operational costs by 30% (Gartner).
• 68% of all customer service and support interactions with technology vendors will be handled by agentic AI by 2028, with 56% of respondents expecting agentic AI to handle over half of interactions within 12 months (Cisco).
• Hostinger’s agentic support assistant Kodee resolved 75% of 750,000 monthly conversations without human intervention as of August 2025, saving over €9 million annually, up from a 50% resolution rate at the start of that year, with average client response time dropping from 28 seconds to 9 seconds (Hostinger).

The near-universal demand for governance frameworks alongside deployment reflects a broader pattern: appetite for agentic AI in customer service is high, but so is awareness of what happens when it operates without guardrails.

Expert tip

The shift from AI that answers questions to AI that takes action is where the real results show up. When we evolved Kodee from a support chatbot into an agent that could act directly inside a client’s account, the improvements were immediate and measurable across every metric we tracked. The governance question matters too: you need clear boundaries on what the agent can and cannot do autonomously before you scale. We learned more from defining those limits carefully than from any model upgrade.

Ričardas Kudirka

Chatbots Project Manager at Hostinger

Software development and IT

Software engineering and IT functions report the highest levels of scaled agentic AI adoption across all industries, and benchmark data shows capability advancing fast.

• AI agent accuracy on OSWorld, a benchmark testing agents on real computer tasks across operating systems, rose from roughly 12% to 66.3% in 2025, coming within six percentage points of human performance. Agents still fail roughly one in three attempts (Stanford HAI AI Index Report).
• On SWE-bench Verified, a coding benchmark testing AI on real GitHub software engineering tasks, performance rose from 60% to near 100% in a single year, the fastest single-year capability gain recorded on a major software development benchmark (Stanford HAI AI Index Report).
• Claude Code processes 195 million lines of code weekly and reached 115,000 active developers as of July 2025. An internal Anthropic survey of 132 engineers reported a 67% increase in merged pull requests per engineer per day and self-reported productivity up 50% (Hostinger’s vibe coding statistics).
• Klarna’s AI agent handled the equivalent workload of 853 full-time employees and saved the company $60 million by Q3 2025, up from 700 FTE equivalents at the start of that year (CX Dive).
• By 2027, agentic AI is projected to require 56% of the workforce to reskill due to AI-driven automation. C-suite executives also anticipate 71% of customer support inquiries handled touchlessly and a 43% increase in real-time supply chain spend visibility (IBM Agentic AI’s Strategic Ascent).

The pace of capability improvement on software benchmarks is particularly striking. Gains of that magnitude in a single year suggest that the productivity figures reported by early enterprise adopters are likely understating what is coming in the next 12 to 24 months.

Healthcare and insurance

Healthcare leads in knowledge management use cases, while insurance leads in marketing and sales, a split that reflects the different compliance constraints and operational pressures each sector faces.

• Healthcare shows strong agentic AI uptake in knowledge management, with 14% of survey respondents reporting scaled use in that function, higher than any other industry for that specific use case (McKinsey Agentic AI Advances).
• In an agentic AI clinical assistant deployment at AtlantiCare, providers saw a 41% reduction in documentation time, saving approximately 66 minutes per day, results that prompted AtlantiCare to expand the tool from ambulatory settings to all of its emergency departments (Oracle Health).
• Insurance leads in agentic AI adoption for marketing and sales use cases, while the healthcare and legal sectors are also seeing rapid agent deployment, according to McKinsey’s industry breakdown (McKinsey Agentic AI Advances).

In both healthcare and insurance, the strongest adoption signals come from high-frequency, structured tasks where the cost of errors is measurable and the volume justifies automation. Documentation, compliance checks, and customer query routing fit that profile precisely, and early trials in both sectors consistently report high adoption rates and clear ROI.

Agentic AI security and governance

Agentic AI deployments are moving faster than the governance frameworks around them. The data from SailPoint’s dedicated security research, which surveyed 353 IT professionals specifically about AI agent risk, makes this concrete:

• 82% of organizations already use AI agents, but only 44% have policies in place to secure them. 96% of technology professionals consider AI agents a growing security risk, while 98% plan to expand their use within the next year (SailPoint).
• 80% of companies say their AI agents have already taken unintended actions, including accessing unauthorized systems (39%), sharing sensitive data without authorization (33%), and downloading sensitive data (32%) (SailPoint).
• 23% of organizations report their AI agents have been tricked into revealing access credentials, and 92% say governing AI agents is critical to enterprise security (SailPoint).

These figures point to a structural problem: organizations are deploying agents faster than they are building the controls to govern them. The SailPoint data is particularly striking given that 98% of the same respondents plan to expand their AI agent use, meaning the risk exposure is set to grow before governance catches up.

• The average responsible AI maturity score increased from 2.0 in 2025 to 2.3 in 2026, but only about one-third of organizations report maturity levels of three or higher in governance and agentic AI controls (McKinsey 2026 AI Trust Maturity Survey).
• Only 31% of organizations’ proprietary data is accessible to AI models, and just 13% is actually used by those models. In response, 77% of executives are investing in data quality and governance improvements (IBM Blueprint for Agentic Operations).
• 45% of executives cite a lack of visibility into agent decision-making processes as a significant implementation barrier, something IBM researchers characterize as a design choice rather than a technical limitation. (IBM Agentic AI’s Strategic Ascent).
• Documented AI incidents rose from 233 in 2024 to 362 in 2025, a 55% year-over-year increase, with responsible AI benchmarks and safety reporting still lagging behind capability benchmarks across almost all leading frontier model developers (Stanford HAI AI Index Report).

The pattern across all of this data is consistent: security and governance are being treated as implementation concerns, bolted on after deployment rather than built in from the start. Organizations that get the order right are the ones seeing the strongest results in IBM’s research.

Expert tip

The biggest mistake organizations make with AI agents is treating them differently from every other privileged system in their environment. An AI agent can send emails, access data, trigger workflows, and make decisions – so it needs clear permissions, defined boundaries, and proper audit trails. The companies that establish these controls from the start aren’t slowing innovation down; they’re creating the foundation that lets them scale AI safely.

Yuliia B.

Security Awareness & Compliance Specialist at Hostinger

Open-source AI agents: adoption and usage

The open-source agentic AI ecosystem has grown faster in the past six months than any prior wave of developer tooling. GitHub stars and OpenRouter token volume tell different stories about what that growth actually means.

• OpenClaw accumulated more than 370,000 GitHub stars by late May 2026, overtaking React to become the most-starred software project in GitHub history since its January 2026 relaunch (OpenClaw).
• Hermes Agent, from Nous Research, crossed 160,000 GitHub stars and attracted 295 contributors within approximately 12 weeks of its February 25, 2026 launch (MarkTechPost).

OpenClaw leads on total GitHub stars, but Hermes Agent has pulled ahead on actual runtime.

• On May 10, 2026, Hermes Agent surpassed OpenClaw as the most-used AI agent on OpenRouter’s global daily rankings, processing 224 billion tokens per day against OpenClaw’s 186 billion. Hermes has since extended that lead and now holds the #1 position globally across productivity, coding agents, personal agents, and CLI agents on the platform (OpenRouter, MarkTechPost).

Hermes Agent converted developer interest into active production use faster than almost any open-source framework in recent memory.

That gap between stars and runtime reflects something real: GitHub stars measure curiosity, token volume measures trust. Both are available for self-hosting on a VPS, keeping data and API keys on your own infrastructure: Hermes Agent hosting and OpenClaw hosting.

The future of agentic AI

The data from 2025 and 2026 establishes agentic AI as a technology in transition: broadly adopted at a surface level, scaling in production at a far smaller fraction of organizations, and generating measurable returns for those who have built the infrastructure to support it.

The forecasts for the next three to five years suggest the production adoption gap will close, but the path runs through governance, data quality, and organizational readiness as much as model capability.

IBM’s research puts a number on what that readiness looks like. Organizations with six foundational capabilities in place, including change management readiness, AI governance, data governance, real-time data integration, system interoperability, and financial integration, are 5.4 times more likely to succeed with autonomous workflow adoption. Change management readiness provides the single greatest individual lift of the six.

The scale of what is coming is significant. By 2027, the number of AI agents in Global 2000 companies is expected to grow tenfold, and the number of token and API calls a thousandfold. By 2029, more than 1 billion AI agents are expected to be in use worldwide, around 40 times the number active in 2025, according to IDC. The US agentic commerce market could reach $300 to $500 billion by 2030, roughly 15–25% of overall ecommerce, as agents move from assisting with product research to completing transactions autonomously.

For teams without large engineering resources, tools like Hostinger Agents make agentic AI accessible without building from scratch – covering tasks from content creation and keyword research to sales outreach and customer communications.

All of the tutorial content on this website is subject to

Hostinger’s rigorous editorial standards and values.

The author

Daniela Chan

Daniela is an Off-Site SEO Specialist with extensive expertise in link building, digital PR, and content optimization. She has led international outreach campaigns across the U.S., Brazil, France, and Spain, securing high-quality backlinks. Follow her on LinkedIn.

The post Agentic AI statistics 2026: Market size, adoption, and growth data appeared first on WEBNET Hosting.

A subscription website locks content, services, or products behind a recurring payment. Members pay you monthly or annually rather than just once.

That recurring model gives you predictable month income, rather than chasing one sale at a time. Subscribers also tend to stay longer and spend more than one-off buyers, so each customer is worth more to your business over time.

To create a subscription website, you’ll need a domain, hosting, a CMS or membership plugin, a payment processor, and content people will pay for. You’ll work through eight steps:

1. Decide on a subscription model
2. Choose a platform
3. Register your domain name
4. Set your prices
5. Connect a chosen payment gateway
6. Restrict your content to members
7. Build the checkout flow
8. Track your key metrics

1. Choose your subscription model

Your subscription model is how you charge members and how you structure their access. Picking it is the first real decision, before any tech.

Expect to spend a day or two here. Getting the model and niche right saves weeks of rework later.

The most common models each earn money in different ways.

• Content or media. Gated articles, videos, or a resource library that people pay to access.
• SaaS (software as a service). A tool that people pay to use every month or annually.
• Membership community. A private space with discussions, events, and exclusive access to various assets.
• Online courses. Structured lessons sold as a one-time or recurring program.
• Physical product boxes. A curated box shipped on a schedule.
• Premium newsletter. Paid email with deeper or earlier content.
• Services on retainer. Ongoing work like coaching or consulting, billed monthly.

Validate the niche before you commit. Look at audience demand, willingness to pay, competitor pricing, and how painful the problem is. A niche where people already pay for something is far easier than one where you have to invent the category.

The common pricing patterns include:

• Single tier: one price, one offer.
• Multi-tier: good, better, best at different price points.

Start with one tier at launch. Multi-tier pricing slows you down and splits your testing. Add it later, when you have paying members and real data on what they value most.

Pick the model that fits your situation. Solo creators with an audience should go content or community, B2B operators should go SaaS or services on retainer, and ecommerce sellers should run a product box.

2. Choose your platform

There are three main ways to create a subscription site: WordPress with a membership plugin, an all-in-one platform, or an AI builder. A custom build with Laravel Cashier or Django plus Stripe is a fourth option, but only if you have the engineering resources.

WordPress paired with a membership plugin is a flexible and widely used option. Common choices include MemberPress and Paid Memberships Pro, as well as LearnDash for courses and WooCommerce Subscriptions for products. It’s a cost-effective and flexible route, with full control and an annual license fee instead of a revenue cut.

A platform like Memberful, Podia, Kajabi, Substack, Patreon, or Mighty Networks bundles hosting, payments, member management, and a public site into one package. You give up some flexibility and pay platform fees, but you handle no maintenance.

An AI builder like Hostinger Horizons handles the code and setup for you. It sits between the two: more flexible than a closed platform, and faster to launch than building a WordPress site from scratch.

On the WordPress route, Hostinger’s managed hosting for WordPress handles caching and updates, keeping your membership plugin running as it processes payments. Managed WordPress hosting applies caching intelligently, excluding login and checkout pages so membership and payment flows work correctly.

Pick based on your budget and how much control you need:

• If you want flexibility under $100 a month, go with WordPress and MemberPress on managed hosting, or Hostinger Horizons for an AI build.
• If you want zero maintenance and can absorb 5–10% platform fees, go with Memberful or Podia.
• If you need custom logic at scale, build your own with Stripe.

3. Register a domain

Buy your domain, point it to hosting, install your CMS, and enable SSL. This step takes a few minutes when your domain and hosting are with the same provider. DNS propagation across providers usually completes in a few hours, although it can take up to 48 or even 72 hours in rare cases.

SSL is non-negotiable for subscription sites. Payment gateways refuse to process recurring billing on unencrypted pages, and modern browsers flag any checkout without HTTPS as unsafe. Set it up before you touch payments.

The exact setup depends on your platform, but the order is the same:

• Register a short, brandable domain. Go with .com if it’s available.
• Point your domain to your hosting or platform.
• Install your CMS, or set up your account on a hosted platform.
• Enable SSL on your domain.
• Log in to your admin dashboard.

Register your domain with the same provider as your hosting. You get fewer moving parts, faster DNS propagation, one dashboard for renewals, and no manual nameserver edits.

For Hostinger users, the 1-click WordPress installer in hPanel sets up your CMS and provisions a free SSL. The certificate activates once your domain points to Hostinger and DNS propagates, not the instant you install WordPress. You’ll need it live before connecting the payment gateway.

4. Set up pricing

Decide your price, billing frequency, trial terms, and tier contents. Most sites land at $5–$50 a month for content and community, and $20–$200 a month for software or coaching. Treat that as a sanity check, not a rule.

Pick a billing cycle. Monthly lowers the entry barrier but leads to more cancellations; annual usually offers a 10–25% discount, locks members in for a year, and improves cash flow. Offer both, and consider defaulting to annual once you have social proof and conversion data to support it.

Decide on the trial. A 7-to-14-day free trial cuts friction but attracts tire-kickers; a 14-to-30-day money-back guarantee draws buyers more likely to commit. No trial is suitable when your price is low or your audience trusts you.

Define what each tier includes, like seats, content, features, and support, and spell it out plainly, since vague descriptions kill conversions. Three patterns cover most launches: one-tier, good/better/best, or freemium with a paid upgrade.

Handle taxes early. EU VAT, US sales tax where you have nexus, and VAT or GST elsewhere all apply to digital subscriptions. Configure your billing tool to collect it, or use a merchant of record like Paddle, which handles tax collection and remittance on your behalf.

5. Connect a payment gateway

Create an account with a payment processor, paste the API keys into your membership plugin, test in sandbox mode, then switch to live. Plan 30–60 minutes. The most common mistake is forgetting to flip from test to live mode before launch.

Stripe is the most widely used gateway for subscription sites, with stronger recurring billing, built-in dunning (automated retries and payment recovery for failed charges), SCA/3D Secure handling, and webhook support. US fees are 2.9% + $0.30 per successful charge. Factor that into your tier pricing so the cut doesn’t eat your margin.

If you built your site with Hostinger Horizons, you can connect Stripe to it directly, with no plugin needed.

PayPal reaches customers who won’t enter their card details anywhere else, but its recurring tools are clunkier and harder to troubleshoot. Add it as a secondary option, not your primary.

Regional gateways fill specific gaps. Mollie is strong in Europe, Razorpay handles India, and Paddle acts as a merchant of record, handling VAT and sales tax globally. Paddle is useful for solo operators selling internationally.

Here are the eight steps, in order:

• Create an account with your chosen gateway.
• Verify the business and connect your bank account.
• Copy the test API keys from the gateway dashboard.
• Paste the keys into your membership plugin’s payment settings.
• Run a sandbox transaction to confirm the subscription is created correctly.
• Set up webhooks so subscription statuses like active, canceled, or past due sync back to your site.
• Configure failed-payment retry rules, typically three to four retries over 7–14 days.
• Switch to live API keys and run a real $1 test charge.

Declined cards are a major hidden source of lost revenue. Automatic retries recover a significant share of those payments without manual intervention.

Pick based on where you sell and who you sell to:

• If you’re a global creator or software company, go with Stripe.
• If your customers prefer PayPal, use Stripe as the primary and PayPal as a secondary.
• If you’re an EU seller who wants VAT handled automatically, choose Paddle as your merchant of record.

6. Gate content

Gating content means your membership plugin restricts access to pages, posts, or files unless a visitor has an active, paid subscription. Mark pages, posts, courses, downloads, and product categories as members-only, set up a member dashboard, and decide whether content drips out or opens all at once.

Most membership plugins use an access rules interface: you select content, like specific posts, categories, or sections, and assign it to one or more tiers. Save the rule, and the plugin checks access on every page load.

Build a simple member dashboard showing the member’s current plan, next billing date, a link to update payment, a cancel or pause option, and links to their content. Most plugins include a default one you can extend.

For courses or onboarding, set up drip content so lessons open over time, like one on day one and the next on day seven. This keeps new members from feeling overwhelmed and, more importantly, creates engagement hooks that help retention with multiple tiers, sets access by tier so each sees only what it paid for.

Always test with a logged-out browser and a separate paying account for each tier. Logged out, a gated page should redirect to sign-up; paid, the content should show. This catches the most common mistake: paid content was left public because a rule was assigned to the wrong tier.

7. Launch the checkout flow

Build the pricing page, connect the sign-up form to your membership plugin and payment gateway, send the welcome email, and redirect new members to their dashboard. Run a real $1 test purchase end-to-end first, so anything broken in checkout or the welcome sequence shows up here, not in front of your first customer.

A high-converting pricing page has a clear price, a short feature list, and one CTA per tier, plus trust signals like testimonials or a guarantee near the checkout button. Long forms and unclear pricing are detrimental to conversions.

Keep the checkout form short. Email, password, payment details – that’s the floor. Every extra field you add cuts completion rates.

Here’s how to launch the checkout flow:

• Build the pricing page with one CTA per tier.
• Connect each CTA to the matching subscription plan in your membership plugin.
• Set the redirect so new members land on their dashboard or welcome page after they pay.
• Write the welcome email, a short message confirming access and pointing them to their dashboard, first lesson, or onboarding checklist.
• Set the welcome email to send within seconds of payment confirmation.
• Run a $1 test purchase from a real card.
• Confirm that the welcome email arrived, the dashboard shows the active plan, and gated content opens.
• Refund the test charge and go live.

Send the welcome email within seconds of payment, not minutes. Early engagement matters for retention, and a delayed welcome misses the window when a new member’s motivation is highest.

8. Track metrics

Track a handful of core metrics from day one so you can catch problems early and see where to invest. Set up a dashboard that shows these six:

• Monthly recurring revenue (MRR). The total predictable income from active subscriptions.
• Churn rate. The percentage of members who cancel each month.
• Average revenue per user (ARPU). MRR is divided by the number of active users.
• Customer acquisition cost (CAC). Your total sales and marketing spend, including tools, ads, and related labor, divided by the number of new paying members in the same period.
• Lifetime value (LTV). The total revenue an average member brings in before they cancel.
• Trial-to-paid conversion. The share of trial users who become paying members.

Check it weekly for sudden problems and monthly to see where to invest. Subscription businesses don’t always fail in week one; they bleed slowly through unchecked churn.

Stripe’s dashboard covers MRR, churn, and ARPU out of the box if Stripe is your gateway. Most membership plugins add their own reports for active members and sign-ups. Google Analytics handles funnel data, such as sign-up page views and conversion rate.

For deeper analysis, ChartMogul layers richer cohort and revenue analysis on top of Stripe and stays free up to $10K in MRR. Baremetrics does the same as a paid option. ProfitWell is free too, but it’s now part of Paddle and works best if Paddle is your billing system.

The first things to optimize are your failed-payment retries, the welcome sequence, and pricing tests, in that order. Each one grows revenue without spending more to get new customers.

Churn is the key metric here. The retention section covers tactics to reduce it.

How much does it cost to create a subscription website?

A realistic year-one budget runs about $250–$500 at the low end and $1,000–$2,400 for a more polished setup. Costs scale with the subscription model you choose, since content libraries are cheaper to run than physical product boxes. 

These figures assume a digital subscription, like content, a community, courses, or software.

Pick based on your budget and how much maintenance you want to handle:

• If your first-year budget is under $500 and you’re happy to set it up yourself, go with WordPress or Hostinger Horizons.
• If you want zero maintenance and can absorb a platform fee, go with an all-in-one platform like Podia or Memberful, from about $39 a month.
• If you’re selling physical product boxes, budget separately for inventory and fulfillment, which will significantly exceed your software costs.

How to reduce churn on a subscription website

Healthy monthly churn is 5–8% for consumer content and community, 3–5% for business software. Above 8% means you’re losing customers faster than most healthy consumer businesses, so fix onboarding before spending more on acquisition.

Annual plans work differently. They usually lose under 2% of subscribers per year, but that’s a yearly figure, so it isn’t directly comparable to the monthly rates above.

Retention work is slower and less visible than acquisition, so it gets neglected until the numbers force it.

Most early member loss hides in failed payments, and the biggest win is matching retries to the decline reason: retry an insufficient-funds card after payday, but prompt an expired-card holder to update their details. The other big wins are exit surveys, a pause option, annual upgrades, and better first-week onboarding.

A short exit survey on the cancellation page, one question with five fixed options and a free-text box, surfaces the top reasons to fix first. A “pause” option before “cancel” helps too: merchants who offer it saw pause usage jump 337%, with three in four subscribers returning, per Recurly’s 2026 State of Subscriptions report.

Offering monthly members a discounted annual upgrade at month three locks in 12 months of revenue, since annual subscribers cancel far less.

The five highest-impact moves on most subscription sites:

• Configure smart dunning, tailoring retries to the reason for the decline rather than using a single flat schedule.
• Replace a plain cancel button with a pause option and an exit survey.
• Send a first-week onboarding sequence of 3–5 emails.
• Move monthly members to an annual plan at month three with a discount.
• Run a quarterly cohort analysis to identify which onboarding week or month has the highest dropout rate, then target that moment specifically.

Best platforms for building a subscription website

The best platforms for a subscription website are WordPress plugins such as MemberPress and Paid Memberships Pro, as well as hosted services such as Podia, Kajabi, Memberful, Substack, and Patreon.

The table compares them by type, starting price, payment support, and suitability.

Pick based on your use case:

• For courses, go with Kajabi or LearnDash on WordPress.
• For a paid newsletter, go with Substack.
• For a community, go with Memberful or Podia.
• For a flexible content site under $300 a year, go with WordPress and MemberPress, or Hostinger Horizons for an AI-assisted setup.

Which is better for a subscription site: WordPress or a SaaS platform?

WordPress wins on cost and flexibility, since you pay a flat hosting and plugin license fee rather than a revenue cut. SaaS wins on speed and zero maintenance, since you don’t manage updates, hosting, or plugin conflicts.

An AI builder like Hostinger Horizons sits between the two. It’s a vibe coding tool that builds apps from prompts, so it can make a membership site, but features like scheduled content, tiers, and member dashboards need prompting rather than coming ready-made like MemberPress or Kajabi.

Here’s a quick way to break the tie:

• If you’re comfortable with the WordPress dashboard and willing to manage updates, go with WordPress.
• If you want to launch in a weekend and never touch a server, go with a SaaS platform.
• If you want custom layouts without having to learn WordPress deeply, go with an AI builder.
• If you expect revenue to exceed $5,000 per month soon, lean toward WordPress or a flat-fee platform like Kajabi, or one of Podia’s higher tiers. The platforms that take a percentage, like Patreon and Memberful, get expensive at scale.

Next steps after launching your subscription website

In your first 30 days, watch trial-to-paid conversion and welcome email open rates daily; they show whether your offer fits and your onboarding lands. If trial-to-paid is under 10% for a consumer subscription, or welcome opens under 40%, look into those first.

Between days 60 and 90, group your members by the month they signed up and compare how many of each group are still subscribed. Your week-one sign-ups are starting to cancel now, and when and why they leave is the most useful data you’ll get.

After six months, add a second tier only if the data supports it, meaning members are asking for more or canceling over missing features. Add a referral or affiliate program once your cancellation rate is healthy, since those incentives are wasted while members are still leaving fast.

Revisit the platform decision only if you hit a hard limit you can name, like a feature you can’t build, a cost that’s become painful at your revenue level, or a performance ceiling. Platform migrations are expensive, so don’t trigger one over a feeling.

All of the tutorial content on this website is subject to

Hostinger’s rigorous editorial standards and values.

The author

Justina Bogužaitė

Justina is a Content Writer passionate about marketing, with a background in social media and customer success management. She also loves reading books, traveling and exploring new places as well as cooking, and trying out new recipes. Follow her on LinkedIn.

The post How to create a subscription website: 8-step guide appeared first on WEBNET Hosting.

The post My Wife Needs a New Laptop appeared first on WEBNET Hosting.

This happens more often than most Linux administrators would like to admit. Maybe a new Nginx release introduced a default configuration change that broke your virtual hosts. A Python library update changed an API that your internal scripts rely on. Or perhaps a kernel update no longer works with a third-party driver.

From DNF’s point of view, everything installed successfully, but that doesn’t always mean your applications will continue to work as expected.

Downgrading a package on RHEL-based distributions is easy when it’s an independent package, but things become more challenging when other packages depend on the newer version, because DNF may also need to downgrade related dependencies to keep the system consistent.

In this guide, you’ll learn how to check which package versions are available, safely downgrade a package, prevent it from being updated again, recover an older package from the local RPM cache, and even roll back an entire DNF transaction if an update caused problems.

How DNF Handles Downgrades

Before you start downgrading packages, it’s useful to understand what DNF does behind the scenes.

Every time you install, update, remove, or downgrade a package, DNF records the operation as a transaction in its history database. This history makes it possible to review previous changes and, in many cases, roll back an entire transaction instead of manually fixing individual packages.

When you run a package downgrade, DNF doesn’t simply replace the newer package with an older one. It first checks whether the older version is compatible with the rest of the packages currently installed on your system.

If another package depends on the newer version, DNF will detect the conflict depending on the situation, it may:

• Downgrade the required dependencies as well.
• Refuse the downgrade because it would break other installed packages.
• Ask for confirmation before making additional changes.

That’s why it’s worth answering two questions before running a downgrade:

• Is the version you want compatible with the packages currently installed on your system?
• Is the older version still available in one of your enabled repositories or in your local package cache?

Taking a minute to check these first can save you from creating even more dependency problems later.

Check What Versions Are Available

Before downgrading a package, check which version is currently installed and whether the older version is still available in your enabled repositories.

To list all available versions of a package, run:

dnf list --showduplicates nginx

Example output:

Installed Packages
nginx.x86_64              1:1.26.2-2.el10             @appstream

Available Packages
nginx.x86_64              1:1.24.0-4.el10             appstream
nginx.x86_64              1:1.26.2-2.el10             appstream

The Installed Packages section shows the version currently installed on your system.

The Available Packages section lists every version that your enabled repositories currently provide. If the version you want appears here, you can downgrade to it.

If it doesn’t, the repository no longer carries that package version. Don’t worry, we’ll cover how to recover older packages from the local RPM cache later in this guide.

If you want more information about the installed package, including the repository it came from, use:

dnf info nginx

Example output:

Installed Packages
Name         : nginx
Epoch        : 1
Version      : 1.26.2
Release      : 2.el10
Architecture : x86_64
Size         : 1.7 M
Source       : nginx-1.26.2-2.el10.src.rpm
Repository   : @System
From repo    : appstream
Summary      : A high performance web server and reverse proxy server
License      : BSD
Description  : Nginx is a web server and a reverse proxy server for HTTP, SMTP,
             : POP3 and IMAP protocols, with a strong focus on high concurrency,
             : efficiency and low memory footprint.

Pay attention to the Version, Release, and Epoch fields. Together, they uniquely identify the package version. If you need to downgrade to a specific release, you’ll use this version information in the downgrade command.

Downgrade to the Previous Version

If you simply want to go back to the previous version of a package, use the dnf downgrade command:

sudo dnf downgrade nginx

Example output:

Dependencies resolved.
================================================================================
 Package      Arch    Version             Repository                      Size
================================================================================
Downgrading:
 nginx        x86_64  1:1.24.0-4.el10     appstream                      42 k

Transaction Summary
================================================================================
Downgrade  1 Package

Total download size: 42 k
Is this ok [y/N]: y

The sudo command runs DNF with administrator privileges, which are required when installing, removing, or downgrading system packages.

The dnf downgrade command automatically selects the highest available version that is older than the one currently installed. Review the transaction summary, and if everything looks correct, press y to continue.

Once the downgrade is complete, verify that the expected version is installed:

nginx -v

Example output:

nginx version: nginx/1.24.0

If the version shown matches the one you expected, the downgrade was successful.

Downgrade to a Specific Version

If you need to downgrade to a version that’s more than one release behind, specify the package name followed by the target version:

sudo dnf downgrade nginx-1.24.0-4.el10

Example output:

Dependencies resolved.
================================================================================
 Package      Arch    Version             Repository                      Size
================================================================================
Downgrading:
 nginx        x86_64  1:1.24.0-4.el10     appstream                      42 k

Transaction Summary
================================================================================
Downgrade  1 Package

Total download size: 42 k
Is this ok [y/N]: y
Downloading Packages:
nginx-1.24.0-4.el10.x86_64.rpm        42 kB/s |  42 kB     00:01
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Downgrading  : nginx-1:1.24.0-4.el10.x86_64                             1/2
  Cleanup      : nginx-1:1.26.2-2.el10.x86_64                             2/2
  Verifying    : nginx-1:1.24.0-4.el10.x86_64                             1/2
  Verifying    : nginx-1:1.26.2-2.el10.x86_64                             2/2

Downgraded:
  nginx-1:1.24.0-4.el10.x86_64

Complete!

The transaction output is easy to follow:

• Downgrading shows the older package version that DNF is installing.
• Cleanup shows the newer version being removed from the system.
• Verifying confirms that the downgrade completed successfully and the RPM database is consistent.

After the transaction finishes, verify the installed version:

nginx -v

If the output shows the version you requested, the downgrade was successful.

Lock the Package Version with versionlock

After downgrading a package, the next dnf update will try to install the latest available version again. If you want to keep the package at its current version, use the versionlock plugin.

sudo dnf install python3-dnf-plugins-core

Once the plugin is available, lock the current version of the package:

sudo dnf versionlock add nginx

To see all locked packages, run:

sudo dnf versionlock list

Example output:

Last metadata expiration check: 0:02:31 ago on Mon Jun 29 11:14:08 2026.
nginx-1:1.24.0-4.el10.*

The .* at the end is a wildcard that matches all architectures of that package version. With the lock in place, future dnf update commands will skip nginx, leaving it at the version you’ve pinned.

When you’re ready to receive updates again, remove the lock:

sudo dnf versionlock delete nginx

Downgrade From a Local RPM File

Sometimes the version you need is no longer available in your enabled repositories. It may have been replaced by a newer release, removed from the repository, or you’re working on a system without internet access.

If you still have the older RPM file, you can install it directly.

First, check whether the package is still available in DNF’s local cache:

find /var/cache/dnf -name "nginx*.rpm"

Example output:

/var/cache/dnf/appstream-3f8c21a9d4b72e01/packages/nginx-1.24.0-4.el10.x86_64.rpm

If you find the version you need, install it by specifying the full path to the RPM file:

sudo dnf install /var/cache/dnf/appstream-3f8c21a9d4b72e01/packages/nginx-1.24.0-4.el10.x86_64.rpm

Example output:

Examining /var/cache/dnf/appstream-3f8c21a9d4b72e01/packages/nginx-1.24.0-4.el10.x86_64.rpm: 1:nginx-1.24.0-4.el10.x86_64
Marking nginx-1.24.0-4.el10.x86_64.rpm as an update to 1:nginx-1.26.2-2.el10.x86_64
Dependencies resolved.
================================================================================
 Package  Arch    Version           Repository                          Size
================================================================================
Downgrading:
 nginx    x86_64  1:1.24.0-4.el10   @commandline                       42 k

Transaction Summary
================================================================================
Downgrade  1 Package
Is this ok [y/N]: y
...
Complete!

Even though you’re installing an RPM file manually, DNF recognizes that the package is older than the installed version and performs a downgrade instead of a normal installation. It also checks dependencies just as it would when installing from a repository.

If you downloaded the RPM from another system or an external source, verify its signature before installing it:

rpm --checksig nginx-1.24.0-4.el10.x86_64.rpm

Use DNF History to Roll Back an Entire Transaction

If a system update broke more than one package, you don’t have to downgrade each package individually. DNF keeps a history of every transaction, making it possible to undo an entire update with a single command.

First, view your recent DNF transactions:

sudo dnf history list

Example output:

ID     | Command line              | Date and time    | Action(s) | Altered
-------------------------------------------------------------------------------
    12 | update nginx              | 2026-06-29 09:14 | Update    |       1
    11 | install httpd             | 2026-06-28 14:22 | Install   |       3
    10 | update                    | 2026-06-27 08:00 | Update    |      47
     9 | install python3-flask     | 2026-06-26 16:44 | Install   |       5

Each transaction has a unique ID. You’ll use this ID if you want to inspect or undo a specific operation.

To see exactly what changed during a transaction, run:

sudo dnf history info 12

Example output:

Transaction ID : 12
Begin time     : Sun Jun 29 09:14:22 2026
Begin rpmdb    : 847:f3a2c...
End time       : Sun Jun 29 09:14:38 2026 (16 seconds)
End rpmdb      : 847:9b14d...
User           : root 
Return-Code    : Success
Command Line   : update nginx
Transaction performed with:
    Installed     rpm-4.19.1-1.el10.x86_64
    Installed     dnf-4.18.0-1.el10.noarch
Packages Altered:
    Upgrade  nginx-1:1.26.2-2.el10.x86_64  @appstream
             nginx-1:1.24.0-4.el10.x86_64  @System

This output shows that transaction 12 upgraded nginx from version 1.24.0 to 1.26.2.

To undo that transaction, run:

sudo dnf history undo 12

After you confirm the transaction, DNF restores the packages to the versions they had before transaction 12 was applied.

If you simply want to undo the most recent DNF transaction, you don’t need to look up its ID:

sudo dnf history undo last

Handle Broken Dependencies After a Downgrade

If you end up in a state where dnf is refusing to install or update anything because of broken dependencies, run a consistency check first:

sudo dnf check

Example output:

nginx-1:1.24.0-4.el10.x86_64 requires nginx-filesystem = 1:1.24.0-4.el10
nginx-filesystem-1:1.26.2-2.el10.x86_64 is a newer version

This output tells you exactly what’s broken and why. In this case, nginx was downgraded but nginx-filesystem wasn’t, so the version requirement is unmet.

Fix it by downgrading the dependency too:

sudo dnf downgrade nginx-filesystem

Run dnf check again to confirm nothing else is broken:

sudo dnf check

No output means the RPM database is consistent and all dependencies are satisfied.

Have you used dnf history undo to recover from a bad update, or found a faster way to track down the right version when the repo no longer carries it? Share it in the comments below.

The post How to Downgrade and Lock Packages With dnf in RHEL Systems appeared first on WEBNET Hosting.

The post 4 Tech Experts Debate PC Questions! appeared first on WEBNET Hosting.

If you chose the Minimal Install option during the Rocky Linux 10 installation, your system includes only the essential packages needed to run without any desktop environment, which means no graphical login screen and no GUI applications.

This setup is ideal for servers because it’s lightweight and uses fewer system resources. However, if you’re using your system as a workstation, a virtual machine, or simply prefer working with a graphical interface, you’ll probably want to install GNOME.

This guide covers two installation methods.

• The first uses DNF to install GNOME from the online repositories, which is the easiest option if your system has internet access.
• The second shows how to install GNOME offline using the Rocky Linux 10 DVD ISO as a local package repository, which is useful for air-gapped systems, secure lab environments, or machines without internet access.

This tutorial was tested on a minimal installation of Rocky Linux 10, but the same installation instructions also work on AlmaLinux 10 and RHEL 10.

What You’ll Need

Before you begin, make sure you have the following:

To check how much free disk space you have, run:

df -h /

Example output:

Filesystem      Size  Used Avail Use% Mounted on
/dev/sda3        40G  3.2G   37G   8% /

Look at the Avail column. If you have at least 3 GB of free space, you’re ready to continue.

Method 1: Install GNOME Online (With Internet Access)

If your Rocky Linux 10 system has an internet connection, you can use the dnf command to download all the required packages directly from the official Rocky Linux repositories.

Step 1: Update Your System

Before installing new software, it’s a good idea to update your existing packages, which ensures you’re installing the latest versions and helps avoid dependency issues.

sudo dnf update -y

The sudo command runs the update with administrative privileges, while the -y option automatically answers yes to any prompts. Depending on the number of available updates and your internet speed, this process may take a few minutes.

Step 2: Install the GNOME Desktop

Rocky Linux groups related packages together, so instead of installing hundreds of individual packages, you can install the complete GNOME desktop with a single command.

sudo dnf group install "Server with GUI" -y

This installs everything needed for a full graphical desktop, including:

• GNOME Shell
• GDM (GNOME Display Manager)
• Wayland
• Desktop utilities and supporting libraries

Tip: If you prefer a smaller desktop installation without the extra server-related tools, install the GNOME group instead:

sudo dnf group install "GNOME" -y

Note: If you receive a No match for group error, list the available package groups first:

sudo dnf group list

Then use the group name shown on your system.

Step 3: Set Graphical Boot as Default

Installing GNOME doesn’t automatically change the system’s default boot mode, because a minimal Rocky Linux installation starts in multi-user.target, which is command-line mode.

First, check the current default target:

sudo systemctl get-default

Example output:

multi-user.target

Now change it to graphical mode:

sudo systemctl set-default graphical.target

You should see output similar to:

Removed "/etc/systemd/system/default.target".
Created symlink /etc/systemd/system/default.target → /usr/lib/systemd/system/graphical.target.

This tells systemd to start the graphical desktop automatically every time the system boots.

Step 4: Start the GUI Without Rebooting

There’s no need to reboot immediately. You can start the graphical login screen right away by starting the GDM service:

sudo systemctl start gdm

After a few seconds, the GNOME login screen should appear, so sign in using the same username and password you use to log into the terminal or SSH.

If the graphical login screen doesn’t appear, check the GDM logs for any errors:

sudo journalctl -u gdm -n 50

On virtual machines, startup problems are often caused by missing graphics drivers or integration tools:

• VirtualBox: Install VirtualBox Guest Additions.
• VMware: Install VMware Tools or Open VM Tools.
• KVM/QEMU: Use the virtio or QXL display adapter for the best compatibility.

Step 5: Reboot and Confirm

Finally, reboot the system to make sure it starts directly in graphical mode.

sudo reboot

After the system restarts, you should see the GNOME login screen automatically. Once you’ve logged in, open a terminal by pressing Ctrl+Alt+T and verify that GNOME is installed:

gnome-shell --version

Example output:

GNOME Shell 47.x

If you see the installed GNOME version, the installation was successful, and your Rocky Linux 10 system is now ready to use with a full graphical desktop.

Method 2: Install GNOME Offline

If your Rocky Linux 10 system doesn’t have internet access, you can install GNOME directly from the Rocky Linux 10 DVD ISO. Instead of downloading packages from online repositories, DNF reads them from the mounted ISO.

Important: Use the Rocky Linux 10 DVD ISO, not the Minimal or Boot ISO, because the DVD image contains the BaseOS and AppStream repositories required to install GNOME.

Step 1: Get the ISO onto the Machine

First, make the DVD ISO available on your system.

If you’re using a virtual machine, attach the ISO as a virtual DVD drive from your hypervisor.

If you’re using a physical server, copy the ISO to the machine. For example:

scp /path/to/Rocky-10-latest-x86_64-dvd.iso user@your-server-ip:/tmp/

Replace:

• user with your login username.
• your-server-ip with the IP address of your Rocky Linux system.

Once the copy finishes, verify that the ISO is present:

ls -lh /tmp/Rocky-10-latest-x86_64-dvd.iso

Step 2: Mount the ISO

Create a directory that will serve as the mount point:

sudo mkdir -p /mnt/rocky10-iso

Now mount the ISO:

sudo mount -o loop /tmp/Rocky-10-latest-x86_64-dvd.iso /mnt/rocky10-iso

You may see a message like this:

mount: /mnt/rocky10-iso: WARNING: source write-protected, mounted read-only.

Next, verify that the mount was successful:

ls /mnt/rocky10-iso/

Example output:

AppStream BaseOS EFI LICENSE RPM-GPG-KEY-Rocky-10 images isolinux media.repo

Make sure you can see both BaseOS and AppStream directories, because these contain all the packages required for the installation.

If they’re missing, you’ve probably mounted the Minimal or Boot ISO instead of the DVD ISO.

Step 3: Create a Local DNF Repo

Create a new DNF repository file:

sudo nano /etc/yum.repos.d/rocky10-local.repo

Paste the following configuration:

[rocky10-baseos-local]
name=Rocky Linux 10 - BaseOS (Local ISO)
baseurl=file:///mnt/rocky10-iso/BaseOS
enabled=1
gpgcheck=1
gpgkey=file:///mnt/rocky10-iso/RPM-GPG-KEY-Rocky-10

[rocky10-appstream-local]
name=Rocky Linux 10 - AppStream (Local ISO)
baseurl=file:///mnt/rocky10-iso/AppStream
enabled=1
gpgcheck=1
gpgkey=file:///mnt/rocky10-iso/RPM-GPG-KEY-Rocky-10

Save the file and exit the editor.

Now disable the online repositories so DNF won’t try to connect to the internet:

sudo dnf config-manager --disable * 2>/dev/null
sudo dnf config-manager --enable rocky10-baseos-local rocky10-appstream-local

Verify that DNF can see the local repositories:

sudo dnf repolist

Example output:

repo id                         repo name
rocky10-appstream-local         Rocky Linux 10 - AppStream (Local ISO)
rocky10-baseos-local            Rocky Linux 10 - BaseOS (Local ISO)

If the repositories don’t appear, double-check:

• The ISO is mounted correctly.
• The baseurl paths match the mount location.
• There are no typing mistakes in the .repo file.

You can also verify that the package directories exist:

ls /mnt/rocky10-iso/BaseOS 
ls /mnt/rocky10-iso/AppStream

Step 4: Install GNOME from the Local Repo

Once the local repositories are working, install GNOME just as you would on an online system:

sudo dnf group install "Server with GUI" -y

DNF will install all required packages directly from the mounted DVD ISO without accessing the internet. Depending on your storage device, the installation usually takes 5 to 10 minutes.

Step 5: Set Graphical Boot and Start GDM

After the installation finishes, configure the system to boot into the graphical interface:

sudo systemctl set-default graphical.target

Start the GNOME Display Manager without rebooting:

sudo systemctl start gdm

The GNOME login screen should appear after a few seconds, so sign in using your normal user account.

Finally, reboot the system to confirm that it starts directly in the graphical desktop:

sudo reboot

Optional: Mount the ISO Automatically at Boot

By default, the ISO is mounted only for the current session. After a reboot, you’ll need to mount it again if you want to install more packages from it.

To mount it automatically during boot, add the following entry to /etc/fstab:

/tmp/Rocky-10-latest-x86_64-dvd.iso  /mnt/rocky10-iso  iso9660  loop,ro  0 0

Before rebooting, verify that the entry is correct:

sudo mount -a

If the command completes without errors, the mount is configured correctly.

Warning: If you move or delete the ISO file after adding it to /etc/fstab, the system may pause during boot while trying to mount it. If you no longer need the ISO, remove the corresponding /etc/fstab entry before deleting or relocating the file.

Switching Back to Text Mode

If you no longer need the graphical desktop, you can configure Rocky Linux to boot back into command-line mode.

First, change the default boot target to multi-user, stop the graphical login manager, and then reboot the system:

sudo systemctl set-default multi-user.target
sudo systemctl stop gdm
sudo reboot

After the reboot, the system will start in text mode and display the login prompt instead of the GNOME login screen.

If you want to switch back to the graphical desktop later, set the default target back to graphical.target and reboot:

sudo systemctl set-default graphical.target
sudo reboot

Alternatively, if you’re currently logged into the command line and don’t want to reboot, you can start the graphical login screen immediately:

sudo systemctl start gdm

Conclusion

You’ve now learned two ways to install the GNOME desktop on Rocky Linux 10. If your system has internet access, installing GNOME with DNF is the quickest and easiest option. If you’re working in an offline or restricted environment, you can use the Rocky Linux 10 DVD ISO as a local repository to install the same desktop without downloading any packages.

Whichever method you choose, you’ll end up with a fully functional GNOME desktop running on a minimal Rocky Linux 10 installation. You also learned how to configure the system to boot into graphical mode by default, switch back to text mode when needed, and troubleshoot common issues during the installation.

If you run into any problems during the installation, such as package errors, GDM failing to start, or display issues inside a virtual machine, leave a comment below with your setup and the exact error message. I’ll be happy to help you troubleshoot the issue.

The post Install GNOME on Rocky Linux 10 Using ISO (Offline) appeared first on WEBNET Hosting.

The post Daily Driving Meta Ray-Ban Display with Neural Handwriting appeared first on WEBNET Hosting.

The post Who has the Worst Monitor at Linus Tech Tips? appeared first on WEBNET Hosting.

The good news is that Linux has several excellent alternatives that offer the same core features, including multi-threaded downloads, browser integration, download scheduling, and the ability to pause and resume downloads.

To help you find the right tool, we’ve put together a list of 10 download managers that are actively maintained and work well on modern Linux distributions in 2026.

If you’re setting up a fresh Linux system and want a solid terminal-based option alongside a GUI tool, check out our guides on command-line download tools and Axel.

1. XDM – Xtreme Download Manager

If you’re coming from Windows and looking for something similar to Internet Download Manager (IDM), XDM is usually the first tool people recommend. It offers multi-threaded downloads, browser integration, download scheduling, and support for resuming interrupted downloads.

XDM can split files into multiple segments and download them simultaneously, which often results in noticeably faster download speeds, especially on large files. Once installed, it can automatically capture downloads from popular web browsers, so you don’t have to manually copy and paste links.

Another useful feature is its built-in video downloader, which can detect videos on sites like YouTube and Vimeo and save them directly to your system. It also includes a video converter, making it easy to convert downloaded videos to MP4, MP3, and other common formats.

Why Choose XDM?

• Fast multi-threaded downloads with up to 32 segments per file.
• Pause and resume support for interrupted downloads.
• Automatic browser integration.
• Video downloading from many popular websites.
• Built-in video conversion tools.
• Support for HTTP, HTTPS, FTP, DASH, HLS, and HDS protocols.
• Clipboard monitoring for automatic link detection.
• Available on Linux, Windows, and macOS.

The easiest way to install XDM is to download the latest package from the official website, extract it, and run the installer:

wget https://github.com/subhra74/xdm/releases/download/7.2.11/xdm-setup-7.2.11.tar.xz
tar -xvf xdm-setup-7.2.11.tar.xz
sudo sh install.sh

After installation, launch XDM from your applications menu and install the browser extension when prompted. Once that’s done, downloads will automatically be handed over to XDM whenever you click a download link.

2. DownThemAll

If most of your downloads happen inside Firefox, DownThemAll is worth a look. Unlike traditional download managers, it runs as a browser extension rather than a standalone application, which makes it lightweight, easy to install, and convenient for users who don’t want another program running in the background.

Where DownThemAll really shines is bulk downloading. Instead of downloading files one by one, it can scan an entire web page and collect all available links, images, videos, documents, and other downloadable files. You can then filter the results and download only the items you need.

This makes it especially useful for downloading image galleries, PDF collections, software mirrors, or large groups of files from a single page. It also supports multiple download connections per file, helping improve download speeds on servers that allow it.

Why Choose DownThemAll?

• Downloads all links, images, and media files from a web page.
• Batch downloads hundreds of files with a few clicks.
• Multiple connections per file for faster downloads.
• Smart filters for selecting specific file types.
• Remembers previous download preferences.
• Built-in SHA1 and MD5 checksum verification.
• Works directly inside Firefox.
• Lightweight and easy to use.

Installing DownThemAll is simple, just open Firefox, visit the Firefox Add-ons store, and click Add to Firefox. Once installed, you’ll find new download options in the browser’s context menu and toolbar.

3. uGet Download Manager

uGet is one of the longest-running download managers available for Linux, and despite its age, it’s still actively used because it’s lightweight, reliable, and easy to set up.

Unlike some modern download managers that focus heavily on flashy interfaces, uGet keeps things simple. It provides all the essential features most users need, including download acceleration, pause and resume support, download scheduling, and clipboard monitoring.

One of uGet’s biggest strengths is its ability to work with aria2, a powerful command-line download engine that provides faster multi-connection downloads, BitTorrent support, and Metalink downloading without significantly increasing resource usage.

Because it uses the GTK toolkit, uGet fits naturally into desktop environments such as GNOME, Cinnamon, MATE, Xfce, and Budgie.

Why Choose uGet?

• Multi-file downloads with per-file or global speed limits.
• Torrent and Metalink file support.
• Anonymous FTP or authenticated FTP download support.
• URL list import from local files.
• Command-line interface support.
• 16 segments per file.
• Clipboard URL monitoring.
• Optional aria2 integration for faster downloads.
• FlashGot add-on integration for Firefox.

To install uGet on Linux, use the following appropriate command for your specific Linux distribution.

sudo apt install uget         [On Debian, Ubuntu and Mint]
sudo dnf install uget         [On RHEL/CentOS/Fedora and Rocky/AlmaLinux]
sudo emerge -a sys-apps/uget  [On Gentoo Linux]
sudo apk add uget             [On Alpine Linux]
sudo pacman -S uget           [On Arch Linux]
sudo zypper install uget      [On OpenSUSE]    
sudo pkg install uget         [On FreeBSD]

4. Persepolis Download Manager

Persepolis started life as a GUI wrapper for aria2, but the latest release (5.x) dropped that dependency entirely, now it runs its own download engine, supports up to 64 simultaneous connections per file, and ships as a standalone Linux bundle you can run with a double-click with no prerequisites needed.

It’s written in Python, open source under GPL, and works on Linux, Windows, macOS, and BSD. Browser extensions are available for Chrome and Firefox.

Features of Persepolis

• Multi-segment downloading (up to 64 connections).
• Download scheduling and queuing.
• SOCKS5 and HTTP proxy support.
• Video finder for YouTube, Vimeo, DailyMotion, and more.
• Standalone Linux bundle with no Python or aria2 install required.
• Browser extension for Chrome and Firefox.

To install Persepolis on Linux, use the following appropriate command for your specific Linux distribution.

sudo apt install persepolis         [On Debian, Ubuntu and Mint]
sudo dnf install persepolis         [On RHEL/CentOS/Fedora and Rocky/AlmaLinux]
sudo emerge -a sys-apps/persepolis  [On Gentoo Linux]
sudo apk add persepolis             [On Alpine Linux]
sudo pacman -S persepolis           [On Arch Linux]
sudo zypper install persepolis      [On OpenSUSE]    
sudo pkg install persepolis         [On FreeBSD]

5. Motrix

Motrix is a clean, modern download manager that supports HTTP, FTP, BitTorrent, and Magnet links out of the box, with up to 10 concurrent download tasks. The interface is the nicest of anything on this list; it has a dark mode, well-organized categories, and doesn’t feel like it was designed in 2009.

It’s built on top of aria2 under the hood, so the download engine is solid. If you want something that looks good and handles torrents without a separate torrent client, Motrix is worth installing.

Features of Motrix

• Supports HTTP, FTP, BitTorrent, and Magnet protocols.
• Up to 10 concurrent download tasks.
• Clean interface with dark mode.
• Available as AppImage, Snap, and AUR package.

Download the Motrix AppImage from the official GitHub releases and run it directly:

chmod +x Motrix-*.AppImage
./Motrix-*.AppImage

Or install via Snap:

sudo snap install motrix

6. KGet Download Manager

KGet is the default download manager for the KDE Plasma desktop, but it runs fine on GNOME and other environments too. It’s straightforward, handles HTTP and HTTPS downloads well, and has solid Metalink support so you can download the same file from multiple mirrors simultaneously for faster speeds.

If you’re already running a KDE-based distro like Kubuntu or KDE Neon, KGet is probably already installed. On other desktops, it pulls in some KDE framework dependencies, which is worth knowing before you install.

Features of KGet

• FTP and HTTP(S) protocol support.
• Pause and resume support.
• Metalink supports multi-mirror downloads.
• KDE Plasma desktop integration.

To install KGet on Linux, use the following appropriate command for your specific Linux distribution.

sudo apt install kget         [On Debian, Ubuntu and Mint]
sudo dnf install kget         [On RHEL/CentOS/Fedora and Rocky/AlmaLinux]
sudo emerge -a sys-apps/kget  [On Gentoo Linux]
sudo apk add kget             [On Alpine Linux]
sudo pacman -S kget           [On Arch Linux]
sudo zypper install kget      [On OpenSUSE]    
sudo pkg install kget         [On FreeBSD]

7. PyLoad Download Manager

PyLoad is designed for unattended downloading. You manage it through a web interface, which means you can queue up downloads on your server, close the browser, and check back later from any device on the network. It’s written in Python, lightweight, and easily extended with plugins.

It works well for one-click hosters and supports a wide range of file hosting services through its plugin system. If you’re running a home server and want something that runs headless, PyLoad is one of the cleaner options.

Features of PyLoad

• Web-based interface accessible from any browser.
• Plugin support for hundreds of file hosting services.
• Lightweight and runs headless.
• Extendable via Python plugins.

Install PyLoad using pip, Python’s package manager. If pip isn’t already on your system, install it first before running this:

pip install pyload-ng

8. JDownloader 2

JDownloader 2 is the tool power users reach for when they’re pulling files from file hosting services. It handles one-click hosters, encrypted container formats (DLC, RSDF, CCF), automatic CAPTCHA solving, and RAR extraction after download, all without you touching it.

It’s written in Java, so it runs on any Linux distro with a JVM. The interface is more complex than most tools on this list, but if you regularly download from services like Mega, Rapidgator, or Google Drive, nothing else comes close. It has around 300 decryption plugins and receives regular automatic plugin updates so things rarely break.

Features of JDownloader 2

• Supports 300+ file hosting services via plugins.
• Automatic CAPTCHA solving with built-in OCR.
• RAR archive extraction with password list search.
• Encrypted container format support (DLC, RSDF, CCF).
• Remote control via my.JDownloader.org from any browser.
• Bandwidth limiting and download scheduling.
• Automatic plugin updates with no manual maintenance.

JDownloader doesn’t have a package in most Linux repos, so install it from the official installer. First, make sure Java is installed. If it’s not on your system yet, install it as shown:

# On Ubuntu/Debian
sudo apt install default-jdk

# On RHEL/Rocky Linux/Fedora
sudo dnf install java-11-openjdk

Then download the JDownloader installer and run it:

chmod +x JDownloader2Setup_unix_nojre.sh
./JDownloader2Setup_unix_nojre.sh

Or install via Flatpak if you have it set up:

flatpak install flathub org.jdownloader.JDownloader

9. AB Download Manager

AB Download Manager is one of the newer tools on this list and is worth paying attention to. Written in Kotlin, it doesn’t use aria2 like most other managers; it has its own download engine that supports multi-segment downloading, browser integration for Chrome and Firefox, and batch downloads with wildcard filtering.

What makes it stand out in 2026 is the cross-platform story. It ships native builds for Linux (DEB and RPM), macOS (with Homebrew support), Windows, and Android, so the same tool follows you across every machine you use. The browser extension captures audio, video, and HLS streams, not just direct file links. Active development with regular releases.

Features of AB Download Manager

• Multi-segment downloading without aria2 dependency
• Browser extension for Chrome and Firefox (captures HLS, audio, video)
• Batch downloads with search and wildcard filtering
• Native Linux, macOS, Windows, and Android builds
• Dark and light themes, including Black theme
• Open source under Apache 2.0 license

Download the .tar.gz from the AB Download Manager GitHub releases and install it as shown:

tar -xvf ABDownloadManager_*.tar.gz
cd ABDownloadManager/bin/
./ABDownloadManager

10. Free Download Manager (FDM)

FDM is not open source, but it’s free and genuinely good. It splits files into segments, downloads them in parallel, handles BitTorrent alongside regular HTTP and FTP downloads, and has solid browser integration.

One thing worth knowing: a 2023 security incident discovered a compromised Linux build had been distributed through FDM’s servers for a period. The issue was addressed, but if you install it, grab it from the official site and verify the checksum. The current builds are clean.

Features of FDM

• Multi-segment file downloading for maximum speed.
• BitTorrent client built in.
• Browser integration for Chrome and Firefox.
• Traffic scheduling and bandwidth controls.
• Available as .deb for Ubuntu/Debian.
• 30 language support.

Download the .deb package and install it:

curl -O https://dn3.freedownloadmanager.org/6/latest/freedownloadmanager.deb
sudo dpkg -i freedownloadmanager.deb

Conclusion

These tools cover the full range of what Linux users actually need from a download manager, whether that’s a GUI that feels like IDM (XDM), a browser extension (DownThemAll), a headless server setup (PyLoad), or something that tears through file hosting services with CAPTCHA solving (JDownloader 2).

Start with XDM if you want the closest thing to a traditional GUI download manager on Linux. If you’re mostly pulling from file hosters or Google Drive, go straight to JDownloader 2, and if you want something modern and actively developed that works across all your devices, AB Download Manager is worth trying.

Have you used any of these on a real system? Or is there one we missed that should be on this list? Drop it in the comments below.

The post 10 Linux Download Managers That Actually Work in 2026 appeared first on WEBNET Hosting.

Preact is a lightweight alternative to React that delivers the same modern development features, including JSX and hooks, while using a much smaller JavaScript footprint.

It follows React’s component-based approach but focuses on faster rendering and reduced browser overhead, improving loading and responsiveness on mobile devices and slower networks.

Modern front-end applications rely on JavaScript, and larger JavaScript files slow down loading, rendering, and page responsiveness. Lightweight frameworks like Preact reduce that overhead by shipping less code and updating the interface more efficiently through virtual DOM rendering.

Developers build Preact applications with reusable components and JSX syntax, which keeps interface code organized and easier to maintain.

Preact also supports hooks for state and lifecycle management, giving developers the same modern workflow as in React applications.

One of Preact’s biggest advantages is its compatibility with React. With the preact/compat layer, many React libraries and existing projects work with minimal changes, making Preact a practical choice for developers who want better performance without changing their entire development approach.

What is Preact?

Preact is a fast and lightweight JavaScript library for building user interfaces. Developers use it to create interactive websites and web applications with reusable components, JSX syntax, and modern front-end workflows similar to React.

Preact keeps the same general development experience while reducing framework size and browser overhead.

Most React concepts work the same way in Preact, including components, props, state management, hooks, and event handling.

Developers who already know React can start using Preact quickly because the API and project structure remain familiar.

Many React libraries also work through the preact/compat layer, which helps teams reduce bundle size without rewriting an entire application.

Preact applications are built from components, which are small, reusable pieces of interface code. A navigation bar, search form, or product card can each exist as separate components that work together to build a complete page.

JSX syntax makes component code easier to read by combining HTML-like markup with JavaScript logic in the same file.

Preact updates the page through virtual DOM rendering. The virtual DOM is a lightweight representation of the real page structure inside the browser.

When data changes, Preact compares the updated virtual DOM with the previous version and updates only the necessary elements on the page.

A shopping cart counter, for instance, updates the number without reloading the entire interface. Smaller updates reduce browser work and improve rendering speed.

One of Preact’s defining features is its small size. The core library is around 3kB, which is significantly smaller than many modern front-end frameworks.

Bundle size directly affects loading speed because browsers must download, parse, and execute JavaScript before users can interact with a page.

Smaller bundles improve startup performance, especially on mobile devices, older hardware, and slower internet connections.

Jason Miller created Preact to provide a simpler and more efficient way to build modern interfaces without sacrificing the developer experience people liked in React.

The library is now widely used in performance-focused web applications, static sites, progressive web apps (PWAs), and embedded interfaces, where reducing JavaScript size improves usability and loading speed.

Preact vs React

Preact and React use very similar development models, but they prioritize different goals.

React focuses on ecosystem depth, long-term scalability, and tooling support.

Preact focuses on smaller bundle sizes, faster startup performance, and lower browser overhead.

Developers write components, manage state, and use hooks in nearly the same way in both libraries.

JSX syntax, component structure, and rendering patterns are familiar across both ecosystems. A developer who knows React can move to Preact with very little adjustment.

The biggest difference in practice is bundle size. Preact’s core library is about 3 to 4 kB when minified and gzipped, while React and ReactDOM together are tens of kilobytes after compression and much larger before optimization.

Smaller bundles reduce download time and browser processing, improving loading speed on slower networks and lower-powered devices.

Performance differences become more noticeable in lightweight applications, mobile-first websites, landing pages, dashboards, and progressive web apps (PWAs).

A smaller framework leaves more room for application code and assets without increasing page weight too quickly.

React has a larger ecosystem, which gives developers access to more third-party libraries, framework integrations, debugging tools, and learning resources.

The main differences between Preact and React:

Choose Preact when loading speed and small bundle sizes are top priorities. A marketing site, embedded widget, ecommerce storefront, or mobile-first application benefits from reduced JavaScript overhead and faster rendering.

Choose React when your project depends on advanced third-party libraries, large development teams, complex state management systems, or enterprise-level tooling.

React’s ecosystem gives teams more flexibility for long-term scaling and integration-heavy applications.

Preact key features

Preact combines fast rendering, reusable components, React-compatible APIs, and modern front-end tooling in a small JavaScript library.

Developers use Preact to build interactive interfaces with lower browser overhead and smaller bundle sizes than many larger front-end libraries.

Lightweight virtual DOM

The virtual DOM is a lightweight JavaScript representation of the user interface. Instead of changing the browser page structure directly after every update, Preact first creates and updates this virtual representation in memory.

Browsers require more work to update the real DOM because each change affects rendering, layout calculation, and visual painting on the page.

Direct DOM manipulation becomes slower as interfaces grow more complex. Preact reduces that overhead by comparing lightweight JavaScript objects before applying updates to the browser.

Preact stores the interface structure in memory and tracks changes there first. A button click, cart update, or search filter change updates the virtual DOM instead of rebuilding the entire page structure immediately.

Smaller calculations inside memory execute faster than repeated browser DOM operations.

Efficient rendering

Preact renders interface updates through a process called diffing. Diffing compares the previous virtual DOM tree with the updated version after data changes.

The comparison process identifies exactly which elements changed between renders. If a user updates the quantity of a single product in a shopping cart, Preact updates only the related number and price instead of re-rendering the entire page.

Selective updates reduce unnecessary browser work and improve rendering speed. Smaller DOM updates also help maintain responsive interfaces during animations, filtering actions, form input, and other interactive behavior.

Efficient rendering becomes more noticeable in interfaces that frequently update. Dashboards, search results, notifications, and live data feeds benefit from faster update cycles because the browser processes fewer changes at once.

Functional components

Preact applications are built from reusable functional components written with JavaScript and JSX. A functional component is a JavaScript function that returns part of the user interface.

Components help developers organize interfaces into smaller, reusable sections. Navigation menus, login forms, buttons, product cards, and search bars can each exist as separate components with their own structure and behavior.

JSX allows developers to describe interface structure directly inside JavaScript code. HTML-like syntax inside components makes layouts easier to read and maintain because markup and rendering logic stay in the same place.

Props allow components to receive dynamic data from other components. A product card component, for instance, can receive a product name, image, and price through props and render different products using the same reusable structure.

Component composition helps developers combine smaller interface pieces into larger layouts. A product page can include separate components for navigation, filters, product listings, reviews, and checkout.

Reusable architecture makes projects easier to scale and maintain over time.

Hooks

Hooks are functions that allow components to manage state, handle side effects, and control dynamic interface behavior.

Hooks add application logic directly into functional components without requiring a separate class-based structure.

State management allows components to store and update changing data. The useState hook manages values for form inputs, counters, dropdown selections, and modal visibility.

A search field, for instance, can update results instantly as the user types.

The useEffect hook handles side effects and external operations. Developers use it to load API data, update the page after user actions, synchronize interface changes, or trigger browser events after rendering.

Hooks also help manage interactive behavior across the interface. Buttons can update counters, forms can validate input while users type, and product filters can refresh visible results immediately after selection changes.

Preact supports familiar React hooks, including useState, useEffect, useMemo, and useContext.

Shared hook APIs simplify migration from React and reduce onboarding time for developers already familiar with React workflows.

Compatibility with React libraries

Preact supports many React libraries through preact/compat, a compatibility layer that maps React-style imports and APIs to Preact.

Developers can reuse large parts of existing React projects while reducing bundle size and browser overhead.

Developers use preact/compat in the following ways:

• Migrating React applications to Preact to reduce JavaScript bundle size
• Keeping familiar React development patterns while working in Preact
• Reusing compatible React components and third-party libraries
• Maintaining similar workflows for teams already familiar with React

React compatibility reduces migration effort, but developers still need to verify library support before switching projects completely.

Some React-specific libraries, advanced APIs, testing environments, and development tools may require additional configuration. Certain tools also work more reliably in standard React environments.

TypeScript support

Preact supports TypeScript for type-safe front-end development. Developers can build typed components, validate props, and improve code consistency across larger applications.

TypeScript helps catch errors during development before code reaches production. Incorrect property values, missing function arguments, and invalid data structures are easier to detect with static type checking.

Typed components also improve developer tooling. Editors can provide autocomplete suggestions, inline documentation, and faster error detection while developers write code.

Larger projects benefit from stronger structure and easier maintenance because types make component behavior more predictable across teams and shared codebases.

Preact integrates with modern TypeScript workflows in a way similar to React, keeping setup and development patterns familiar.

Modern JavaScript support

Preact supports modern front-end development features such as JSX, ES modules, and modern JavaScript syntax. Developers can integrate Preact into current workflows without changing standard front-end tooling practices.

JSX simplifies component rendering by allowing developers to define interface structure directly inside JavaScript. ES modules organize application code into reusable imports and exports, which improves project structure and maintainability.

Modern JavaScript syntax, such as arrow functions, destructuring, async functions, and template literals, works naturally inside Preact applications. Developers can build applications using the same language features commonly used across modern front-end ecosystems.

Preact also integrates with popular build tools and package management workflows.

Development environments using Vite, Webpack, Babel, npm, or pnpm support Preact without major configuration changes.

Compatibility with modern tooling helps developers adopt Preact more efficiently within existing front-end projects.

Why developers use Preact

Developers choose Preact because it delivers modern front-end features in a much smaller package than many larger JavaScript libraries and frameworks.

The following features are where Preact provides the biggest practical advantages:

• Small bundle size – Preact’s core library is around 3kB gzipped. Smaller JavaScript bundles reduce download time, browser parsing time, and script execution overhead, which helps pages load faster.
• Faster performance – Lightweight rendering and efficient virtual DOM updates improve interface responsiveness. Faster updates are especially useful on mobile devices, slower networks, and lower-powered hardware.
• Lower memory usage – Smaller framework overhead reduces runtime memory consumption. Resource-constrained devices benefit from lighter browser workloads and fewer processing demands.
• React compatibility – The preact/compat package allows many React libraries and components to work with Preact. Developers can keep familiar React-style workflows while reducing application size.
• Modern development support – Preact supports JSX, hooks, TypeScript, ES modules, and modern JavaScript syntax. Common front-end tools such as Vite, Babel, and Webpack also integrate smoothly into Preact projects.
• Good fit for lightweight applications – Preact works well for static sites, progressive web apps (PWAs), embedded widgets, dashboards, and performance-focused front-end applications where keeping JavaScript size low improves loading speed and responsiveness.

What are Preact’s use cases?

Preact is commonly used for lightweight front-end applications that benefit from smaller JavaScript bundles, faster rendering, and lower browser overhead.

Developers use it in projects where loading speed, responsiveness, and efficient resource usage directly affect the user experience. These include:

• Progressive web apps (PWAs) – Preact works well for PWAs that need fast startup performance, responsive navigation, and smooth mobile interaction. Smaller bundles help applications load more quickly on unstable mobile connections and lower-powered devices.
• Static websites – Marketing sites, documentation platforms, blogs, and content-driven websites benefit from Preact’s lightweight runtime. Faster page interaction and reduced JavaScript processing improve responsiveness after the initial page load.
• Embedded applications and widgets – Lightweight dashboards, chat widgets, search tools, pricing calculators, and interactive product blocks fit well with Preact’s small footprint. Smaller embedded applications place less strain on the host page and reduce browser resource usage.
• Mobile-first applications – Mobile-focused interfaces benefit from reduced browser processing and faster rendering performance. Preact helps improve responsiveness on slower networks, older smartphones, and devices with limited memory or processing power.
• React-compatible projects – Existing React projects can use Preact through preact/compat to reduce bundle size while keeping similar component patterns and development workflows. Compatibility support also allows developers to reuse many React libraries and components without rebuilding the application structure from scratch.

What are the limitations of Preact?

Preact prioritizes lightweight performance and small bundle sizes, so it comes with trade-offs in compatibility, tooling, and ecosystem depth. Developers should check these limits before replacing React in a complex project.

• React library compatibility – Preact does not cover every React library or advanced API. Some React-specific packages require additional setup, while others work more reliably in a React project.
• Smaller ecosystem – React has more plugins, tutorials, integrations, debugging tools, and community resources. Preact still has strong core features, but developers may find fewer ready-made examples or package-specific guides.
• Debugging differences – Some React debugging workflows need adjustment in Preact. React DevTools support, testing setups, and framework-specific debugging tools may require additional configuration depending on the project setup.

How to deploy your Preact application

Preact applications need to be built into optimized production files before deployment. The build process prepares your application for faster loading, smaller asset sizes, and production-ready performance.

1. Run the production build command

Build the application with:

npm run build

The command generates optimized production files, usually inside a dist/ or build/ folder, depending on your project setup and build tool.

2. Upload the production files

Upload the generated dist/ or build/ folder to your hosting platform. Static hosting providers serve these files directly to visitors through a CDN or web server.

3. Configure SPA fallback routing if needed

Applications that use client-side routing need SPA (single-page application) fallback routing. A direct visit to routes such as /dashboard or /settings/should load the main application entry file instead of returning a 404 error.

4. Deploy through your hosting provider

Deploy the application through Hostinger web app hosting or another hosting provider that supports modern JavaScript front-end applications. Hostinger enables developers to host a web application using static hosting workflows, Git-based deployments, and modern front-end build environments.

All of the tutorial content on this website is subject to

Hostinger’s rigorous editorial standards and values.

The author

Ksenija Drobac Ristovic

Ksenija is a digital marketing enthusiast with extensive expertise in content creation and website optimization. Specializing in WordPress, she enjoys writing about the platform’s nuances, from design to functionality, and sharing her insights with others. When she’s not perfecting her trade, you’ll find her on the local basketball court or at home enjoying a crime story. Follow her on LinkedIn.

The post What is Preact and how it works appeared first on WEBNET Hosting.

A real estate newsletter is a recurring email sent by agents and brokers to share property updates, local market insights, homeownership advice, and community information with buyers, sellers, homeowners, and past clients.

Building local authority, promoting listings, educating buyers and sellers, staying in touch with past clients, and generating referrals all require different newsletter formats.

Real estate newsletter examples, customized for different objectives:

1. Building local authority – Local market update, neighborhood spotlight, local events, and local business recommendation newsletters.
2. Promoting listings – New listing, just sold, and open house invitation newsletters.
3. Educating buyers and sellers – Buyer education, seller preparation, home valuation, and mortgage and affordability newsletters.
4. Staying in touch with past clients – Homeowner maintenance and personal agent note newsletters.
5. Generating referrals and repeat business – Client success story and referral newsletters.
6. Supporting investment-focused audiences – Investor and rental market newsletters.

1. Local market update newsletter

A local market update newsletter explains recent prices, inventory, demand, and sales trends in a specific area.

Agents use this format to demonstrate local expertise while giving buyers and sellers information they can apply to current decisions.

Start with the key market numbers, then tell readers why they matter. If inventory is increasing, explain how that affects buyers.

If homes are selling quickly, explain what sellers should expect. Readers can find raw data online. Your value lies in helping them understand how current market conditions affect their next move, and whether the market currently favors buyers, sellers, or neither.

Local market update newsletter example:

Subject: June Market Update: More Homes Available as Inventory Grows

Hi Sarah,

The local housing market added more inventory during June, giving buyers additional options across several neighborhoods.

Median home price: $485,000 (+4% month over month)
Active listings: 89 homes (up from 72 last month)
Homes sold: 41
Average days on market: 24 days

More available listings have reduced competition on some properties, although well-priced homes continue to sell quickly.

Homeowners who want to know how current market conditions affect their property's value can request a complimentary home valuation. 
Buyers can review the latest listings to see what's newly available in the area.

CTA:[Request a Home Valuation]
CTA:[Browse Current Listings]

2. Neighborhood spotlight newsletter

A neighborhood spotlight newsletter introduces one local area and explains its real estate appeal.

Use this format to help buyers compare neighborhoods before narrowing their home search.

Focus on the details that shape a buyer’s decision: home prices, recent sales, commute access, schools, parks, restaurants, property styles, and current buyer demand.

Don’t turn the newsletter into a generic area description.

Show readers what living there is like and why the neighborhood meets specific needs, such as shorter commutes, walkable neighborhoods, larger lots, or access to well-rated schools.

Neighborhood spotlight newsletter example:

Subject: Neighborhood Spotlight: Why Buyers Are Looking at Brookside
Hi Daniel,
Brookside continues to attract buyers who want tree-lined streets, older homes with character, and quick access to downtown.
Recent sales in the area have ranged from $420,000 to $675,000, with most homes selling within three weeks when priced well. 
Buyers will find a mix of renovated bungalows, brick colonials, and smaller starter homes near the park.
The neighborhood also offers an easy commute to the city center, several local cafés, weekend farmers markets, and access to Brookside Elementary.
If Brookside is on your list, now is a good time to compare what is available before more spring buyers enter the market.
CTA:[View Homes in Brookside]

3. New listing newsletter

A new listing newsletter promotes a property that has just entered the market to relevant buyers.

Match the listing to the right audience before you send it. A downtown condo appeals to different buyers than a four-bedroom suburban home, so highlight the details that matter most to that group.

Condo buyers may care most about walkability, transit access, and low-maintenance living, while buyers looking for a larger home may focus on square footage, yard space, schools, and room for a growing family.

Include the property’s location, price, key features, and the strongest reason to consider it.

Make it easy for interested buyers to take the next step by showing availability and a clear call to action.

New listing newsletter example:

Subject: Just Listed: 3-Bedroom Home in Maple Grove Under $500,000
Hi Jennifer,
A new listing in Maple Grove just became available and matches the price range and home features you've been searching for.
Located on Oak Ridge Drive, this three-bedroom, two-bathroom home is listed at $489,000 and includes an updated kitchen, a fenced backyard, and a two-car garage. 
The property is less than 10 minutes from downtown and within walking distance of Maple Grove Park.
Showings begin this Saturday, with appointments available throughout the weekend.
CTA:[View Property Details]
CTA:[Schedule a Showing]

4. Just sold newsletter

A just-sold newsletter uses a recent sale to provide nearby homeowners with useful pricing or demand context.

Recent sales give homeowners a clearer view of what buyers are willing to pay for similar properties in their area.

Focus on the details that homeowners care about most: property type, neighborhood, sale price, days on market, and buyer demand.

A recent sale becomes more meaningful when you explain what happened behind the listing.

Did the property sell quickly? Did it attract multiple offers? Did it close near or above the asking price?

Connect the result to the local market so homeowners can better understand how current conditions may affect their own property’s value.

Just sold newsletter example:

Subject: Just Sold Near You: Maple Grove Home Sells in 12 Days

Hi Sarah,

A four-bedroom home on Cedar Lane in Maple Grove recently sold for $612,000 after spending just 12 days on the market.

The property attracted strong buyer interest thanks to its updated kitchen, finished basement, and location near Maple Grove Elementary. 

Multiple buyers submitted offers during the first week, resulting in a sale above the original asking price.

Sales activity like this suggests that well-presented homes in Maple Grove continue to attract qualified buyers and move quickly.

Curious what your home could be worth in today's market?

CTA:[Request a Home Value Estimate]

5. Open house invitation newsletter

An open house invitation newsletter encourages buyers, neighbors, and local contacts to attend an upcoming open house event.

Open houses create an opportunity to generate interest before a property goes under contract and give prospective buyers a chance to experience the home in person.

Lead with the essentials: the date, time, location, and a few standout features that make the property worth visiting.

Help readers quickly decide whether the home fits their needs by mentioning the ideal buyer profile. Help readers quickly decide whether the home belongs on their shortlist.

Mention the property’s price range, layout, or other factors that influence buying decisions. Include clear access details and a simple RSVP or calendar link so interested attendees can plan ahead.

Open house invitation newsletter example:

Subject: Open House This Saturday: Updated Family Home in Maple Grove

Hi Jennifer,

You're invited to tour a newly listed four-bedroom home in Maple Grove this Saturday from 11:00 AM to 2:00 PM.

Located at 145 Cedar Lane, this property features an updated kitchen, a finished basement, a large backyard, and over 2,400 square feet of living space. 

Buyers looking for extra room, access to highly rated schools, and a convenient commute to downtown will want to add this home to their list.

Guests can stop by at any time during the open house. If you plan to attend, please reserve a spot so we can share updates and property information before the event.

Know someone looking for a home in Maple Grove? Feel free to forward this invitation.

CTA:[RSVP for the Open House]
CTA:[Add to Calendar]

6. Buyer education newsletter

A buyer education newsletter explains one part of the homebuying process to help leads move forward with confidence.

Buying a home involves a series of financial and legal decisions, and uncertainty at any stage can slow progress.

Choose one topic per newsletter and explain it in plain language. For instance, pre-approval, down payments, inspections, contingencies, closing costs, offer strategy, and comparing homes all work well because they answer questions buyers encounter during an active search.

Keep the focus practical. Instead of defining terms, explain what buyers should expect, what documents they may need, and how the step fits into the broader purchasing process.

Buyer education newsletter example:

Subject: What Pre-Approval Actually Means for Homebuyers

Hi Jessica,

Pre-approval is one of the first steps in the homebuying process because it helps you understand your budget before you start touring properties.

During pre-approval, a lender reviews your income, debts, credit history, and financial documents to estimate how much you may be able to borrow. 

Sellers also view pre-approved buyers more favorably because financing has already been reviewed.

Getting pre-approved does not commit you to a loan. It gives you a clearer price range and helps you act more quickly when you find a home you want to purchase.

If you're planning to buy within the next year, we can walk you through the pre-approval process and connect you with trusted local lenders.

CTA:[Schedule a Buyer Consultation]

7. Seller preparation newsletter

A seller-preparation newsletter helps homeowners prepare before listing their property. The work that happens before a home reaches the market has a direct impact on buyer interest, showing activity, and perceived value.

Focus on practical steps homeowners can take before professional photos and showings begin. Pricing, repairs, staging, curb appeal, decluttering, photography preparation, inspection concerns, and listing timing are all worth covering.

Keep the advice specific and actionable. Sellers need a clear next step that helps them prepare their home for a successful launch.

Seller preparation newsletter example:

Subject: Thinking About Selling? Start With These Three Steps
Hi Michael,
Preparing your home before listing can make a significant difference in how buyers respond during the first weeks on the market.
Start by addressing visible maintenance issues, such as chipped paint, loose fixtures, or damaged flooring. 
Next, remove unnecessary furniture and personal items to help buyers focus on the space itself. 
Finally, improve curb appeal by tidying landscaping, cleaning walkways, and ensuring the home's exterior makes a strong first impression.
Completing these steps before photography and showings begin can help your property present more effectively when buyers start comparing options.
If you're considering a sale this year, we can walk through your property and identify improvements that deserve attention before listing.
CTA:[Request a Pre-Listing Walkthrough]

8. Home valuation newsletter

A home valuation newsletter explains what affects property value and when homeowners should request a custom estimate.

Homeowners are naturally curious about what their property is worth, but online estimates rarely tell the full story.

Use this format to explain the factors that influence value in your market. Comparable sales provide a starting point, but condition, upgrades, inventory levels, buyer demand, and neighborhood trends all play a role.

A renovated kitchen, a new roof, or a shortage of available homes can affect pricing in ways that automated valuation tools may not fully capture.

Position the newsletter as an update rather than a sales pitch, then give homeowners an opportunity to request a personalized assessment based on current market conditions.

Home valuation newsletter example:

Subject: Quarterly Home Value Update: What's Influencing Prices Right Now?

Hi Sarah,

Home values in Maple Grove continued to benefit from limited inventory and steady buyer demand during the last quarter.

Recent comparable sales show that updated homes are commanding stronger prices than similar properties that require significant improvements. 

Properties with modern kitchens, renovated bathrooms, and move-in-ready condition continue to attract the most interest from buyers.

Online valuation tools can provide a rough estimate, but they don't account for your home's current condition, upgrades, lot characteristics, or recent improvements.

If you'd like a more accurate picture of what your home could be worth in today's market, request a personalized valuation based on recent local sales.

CTA:[Request a Personalized Home Valuation]

9. Mortgage and affordability newsletter

A mortgage and affordability newsletter discusses how changes in financing affect buying power and real estate decisions.

Small changes in interest rates can have a meaningful impact on monthly payments, purchasing budgets, and the types of homes buyers can realistically consider.

Focus on what current financing conditions mean in practical terms. Interest rates, down payment requirements, loan programs, and monthly payment estimates all influence affordability, but numbers alone rarely provide enough context.

Show readers how a rate change affects purchasing power, or how different loan options may change their budget.

The goal is to help buyers adjust their search strategy to current market conditions rather than rely on outdated assumptions about what they can afford.

Mortgage and affordability newsletter example:

Subject: Affordability Update: What Current Rates Mean for Buyers

Hi Jessica,

Mortgage rates have changed in recent months, and that shift may affect how much home you can comfortably afford.

For example, a buyer financing a $400,000 home today could face a different monthly payment than a buyer who secured a mortgage several months ago. 

Changes like these influence purchasing power and may affect the neighborhoods, property types, or price ranges worth considering.

Several loan programs also offer lower down payment options for qualified buyers, making homeownership accessible to those still building savings.

If you haven't reviewed your budget recently, now is a good time to revisit your price range and financing options.

CTA:[Speak With a Lender]
CTA:[Review Your Buying Budget]

10. Homeowner maintenance newsletter

A homeowner maintenance newsletter keeps homeowners informed about seasonal tasks, preventative maintenance, and improvements that help protect their property’s value.

Regular maintenance protects a property’s condition, helps prevent costly repairs, and supports long-term resale value.

Tie the advice to the season so the recommendations look relevant and actionable. Spring maintenance may focus on landscaping and exterior inspections, while fall updates can cover gutter cleaning, weatherproofing, and heating system checks.

Energy-efficiency upgrades, renovation planning, safety inspections, and preventative repairs also work well.

Keep the list manageable. A handful of practical tasks is more useful than an exhaustive checklist that homeowners are unlikely to complete.

Homeowner maintenance newsletter example:

Subject: Fall Home Maintenance Checklist for Homeowners
Hi Sarah,
Fall is a good time to tackle a few maintenance projects before colder weather arrives.
Inspect and clean gutters to prevent water damage. Check doors and windows for drafts that could increase heating costs. 
Schedule a furnace inspection, replace HVAC filters, and trim trees or branches that could become a problem during winter storms.
Small maintenance projects completed now can help prevent larger repair expenses later and keep your home in strong condition throughout the season.
Need a reliable contractor, HVAC technician, or landscaper? We're happy to share recommendations from local professionals that homeowners have used in the area.
CTA:[Request Local Contractor Recommendations]

11. Local events newsletter

A local events newsletter shares community activities that help readers stay connected to the area.

Real estate is ultimately local, and community updates give you a reason to stay in touch even when no one is actively buying or selling.

Focus on events that residents are likely to attend or discuss with friends and neighbors.

Farmers’ markets, school activities, festivals, charity fundraisers, business openings, sports events, and neighborhood gatherings all work well.

A good local events newsletter should be curated. Instead of listing everything happening in town, highlight a handful of events that reflect the character of the community and give readers a reason to explore the area.

Local events newsletter example:

Subject: What's Happening This Weekend in Maple Grove

Hi Sarah,

If you're looking for something to do this weekend, here are a few local events worth checking out:

Maple Grove Farmers Market | Saturday, 8:00 AM–1:00 PM
Summer Concert in the Park | Saturday, 6:00 PM
Maple Grove Youth Soccer Tournament | Sunday, 9:00 AM
Grand Opening of Oak Street Coffee | All weekend

Whether you're new to the area or have lived here for years, local events are a great way to support community businesses and meet your neighbors.

Have a favorite local restaurant, coffee shop, or weekend activity? Reply and let us know. 
Know someone planning a move to Maple Grove? Feel free to forward this email their way.

CTA:[Reply With Your Favorite Local Spot]

12. Local business recommendation newsletter

A local business recommendation newsletter highlights trusted restaurants, shops, service providers, or neighborhood businesses.

Recommendations like these help readers discover new places while reinforcing your connection to the community you serve.

Choose businesses you genuinely know and can speak about from experience.

Explain what makes the business worth visiting, who might benefit from it, and why it stands out locally.

Local business recommendation newsletter example:

Subject: Three Local Businesses Worth Checking Out This Month

Hi Sarah,

Here are three local businesses that have been getting plenty of attention around Maple Grove recently:

Oak Street Coffee – A neighborhood coffee shop known for small-batch roasting, comfortable workspaces, and friendly staff. It's a great spot for remote work or weekend catchups.

Green Leaf Garden Center — A local favorite for seasonal plants, landscaping supplies, and gardening advice. Homeowners looking to refresh their outdoor spaces will find plenty of inspiration here.

Riverfront Books — An independent bookstore with regular author events, book clubs, and a carefully curated selection of new releases and local titles.

Part of what makes a community special is the people and businesses that shape it every day.

Have a favorite local business we should feature in a future newsletter? Reply and let us know.

CTA:[Reply With Your Recommendation]

13. Client success story newsletter

A client success story newsletter shows how an agent helped a buyer, seller, investor, or homeowner solve a real estate challenge.

Real examples help readers see how a strategy works in practice and what results are possible under similar circumstances.

Focus on the journey rather than the outcome alone. Start with the client’s goal, explain the challenge they faced, and walk readers through the approach that helped move things forward.

A quick sale, a winning offer, or a successful investment purchase becomes more meaningful when readers understand the decisions behind the result.

End with a takeaway that readers can apply to their own situation and an invitation to discuss a similar plan.

Client success story newsletter example:

Subject: How One Seller Moved in 30 Days Without Sacrificing Price

Hi Sarah,

A recent client needed to relocate for work and wanted to sell their home quickly without accepting a below-market offer.

After reviewing recent sales, we adjusted the pricing strategy, completed a few low-cost cosmetic updates, and scheduled professional photography before the property went live. 

The home attracted strong interest during the first week and received multiple offers shortly after listing.

The property sold within 30 days at a price that met the seller's goals and timeline.

Every move comes with different priorities. Some homeowners want the highest possible price, while others need certainty, speed, or flexibility.

If you're planning a move and want to explore your options, let's build a strategy that fits your situation.

CTA:[Schedule a Planning Consultation]

14. Referral newsletter

A referral newsletter gives past clients a simple reason to recommend you when someone in their network starts thinking about a move.

People may not be thinking about your services every day, but they often know someone preparing for a move, exploring a purchase, or considering a sale.

Make the referral opportunity specific. Relocations, upsizing, downsizing, inherited properties, investment purchases, and upcoming listings all provide natural reasons to reach out.

A simple reminder is usually enough. Readers already know what you do. The goal is to help them recognize situations where a friend, family member, coworker, or neighbor could benefit from a conversation.

Referral newsletter example:

Subject: Know Someone Planning a Move This Year?

Hi Sarah,

Many real estate conversations start long before a home is listed or a buyer begins touring properties.

A friend may be relocating for work. A family member may need more space for a growing household. 
A neighbor may be thinking about downsizing or preparing to sell after many years in the same home.

If someone in your network is considering a move, I'd be happy to answer questions, discuss options, and help them create a plan that fits their goals.

The best introductions often start with a simple conversation.

Feel free to forward my contact information to anyone who could use real estate guidance.

CTA:[Forward My Contact Information]

15. Investor and rental market newsletter

An investor and rental market newsletter shares rental trends, income-property insights, and investment opportunities.

Investment decisions depend on numbers as much as properties, so investors value market updates that help them evaluate risk, income potential, and long-term growth.

Focus on the metrics that influence returns. Rental demand, vacancy rates, neighborhood growth, cash flow potential, property management considerations, and cap rates all help investors assess opportunities.

Keep the analysis practical. Instead of presenting market data in isolation, explain how one neighborhood compares with another or where investors may find stronger rental demand, lower vacancy risk, or better income potential.

The goal is to help readers identify opportunities worth investigating further.

Investor and rental market newsletter example:

Subject: Investor Update: Comparing Two Rental Markets in Maple Grove
Hi David,
Investors looking for rental properties have been paying close attention to two neighborhoods: Brookside and River Park.
Brookside continues to attract tenants seeking walkable streets, local businesses, and shorter commutes. 
Average rents remain strong, although purchase prices have increased over the past year.
River Park offers lower entry prices and several value-add opportunities for investors willing to renovate older properties. 
Rental demand has remained steady, and recent infrastructure improvements have increased interest in the area.
Both neighborhoods present opportunities, but the right choice depends on your investment goals, budget, and expected holding period.
If you're considering an investment purchase, we can build a shortlist of properties that match your target price range and return objectives.
CTA:[Request an Investment Property Shortlist]

16. Personal agent note newsletter

A personal agent note newsletter gives readers a perspective on what’s happening in the local market or community.

Unlike listing announcements or market reports, this format gives readers a chance to hear directly from you and stay connected between transactions.

Keep the message relevant to real estate, homeownership, the local market, or the community.

A brief observation, recent trend, common client question, or market lesson works well because it gives readers something useful to think about.

The strongest personal notes feel conversational without becoming overly personal. The best personal notes feel relevant and timely. Readers should recognize a market trend, homeowner concern, or community development that affects their own situation.

Personal agent note newsletter example:

Subject: A Quick Observation About This Spring's Market

Hi Sarah,

One trend I've been watching this spring is the widening gap between move-in-ready homes and those that need significant updates.

Well-prepared properties continue to attract strong interest and generate showings quickly, while homes that require major work often take longer to find the right buyer. 
Presentation, pricing, and preparation remain some of the most important factors influencing results.

If you're thinking about buying, selling, or making improvements to your home this year, now is a good time to start planning ahead rather than waiting until you need to make a decision.

Have a question about the local market or your home's value? Just reply to this email. I'd be happy to help.

CTA:[Reply With a Question]

What should a real estate newsletter include?

A real estate newsletter should include content that helps readers understand the market, make property decisions, maintain their home, or stay connected locally.

The best email newsletter practices include:

• Clear audience – Write for buyers, sellers, homeowners, investors, past clients, or local residents. Content becomes more relevant when you know exactly who you’re addressing.
• Local market context – Include pricing trends, inventory changes, recent sales, buyer demand, or neighborhood activity that helps readers understand current conditions.
• Useful real estate advice – Answer one practical question about buying, selling, financing, homeownership, or property values instead of covering multiple topics at once.
• Community relevance – Share local events, business recommendations, neighborhood developments, or community updates that readers will find useful.
• Specific call to action – Give readers a clear next step, such as requesting a valuation, viewing listings, scheduling a consultation, RSVP’ing for an event, replying with a question, or forwarding the email.
• Agent point of view – Add your interpretation of the market or community rather than simply reporting information. Readers can find data elsewhere. Your perspective is what makes the newsletter useful and distinctive.

How often should real estate agents send newsletters?

Real estate agents should send newsletters often enough to stay visible without sending repetitive or low-value emails.

The right schedule depends on how you segment your email list, how quickly information changes, the type of content you’re sharing, and your ability to publish consistently.

Still, there are some general rules that can help you decide on the frequency:

• Weekly – Best for active buyers, new listings, open houses, fast-moving markets, and local event roundups. Information changes quickly, so more frequent updates remain relevant.
• Biweekly – A good fit for engaged leads who are researching the market, learning about the buying or selling process, or preparing for a future move.
• Monthly – Works well for past clients, homeowners, referral contacts, and broader local audiences. Monthly newsletters provide enough touchpoints to stay visible without overwhelming readers.
• Quarterly – Best for in-depth home value updates, market recaps, investment reports, or long-term market analysis that doesn’t require frequent updates.

If you’re unsure where to start, choose a monthly schedule and focus on quality. A newsletter that consistently delivers useful local information is more valuable than a higher-frequency schedule that becomes difficult to maintain.

Which real estate newsletter format should you use?

The right real estate newsletter examples depend on whether your audience is buying, selling, owning, investing, relocating, or staying connected locally.

Different audiences have different questions, priorities, and timelines, so the most effective newsletter format is usually the one that matches what readers are trying to accomplish right now.

Choose newsletter formats based on both audience stage and business goal:

• Buyer leads – Use new listing newsletters, open house invitations, buyer education content, mortgage and affordability updates, and neighborhood spotlights.
• Seller leads – Focus on local market updates, just-sold newsletters, seller preparation tips, and home valuation updates that help homeowners evaluate their options.
• Past clients – Stay connected with homeowner maintenance tips, local events, referral newsletters, and occasional personal agent notes.
• Investors – Share rental market updates, investment property opportunities, neighborhood growth trends, financing updates, and cash-flow considerations.
• Local residents – Highlight community events, local business recommendations, neighborhood updates, and market snapshots that keep readers informed about what’s happening nearby.

How to build a repeatable real estate newsletter campaign

Building a repeatable real estate newsletter campaign requires a consistent, value-first structure.

When creating a real estate newsletter, establish a predictable schedule, build a clean and mobile-friendly template, follow the 90/10 content rule (90% local insights and advice, 10% promotions), and use reliable software to automate delivery.

The easiest way to sustain a real estate email newsletter is to create a repeatable framework. Instead of starting from scratch every time, decide which sections appear in each edition and rotate content based on your audience.

For example, a monthly newsletter might include a local market update, one homeowner tip, a neighborhood spotlight, and a community event. As your real estate email marketing program grows, this structure makes planning, writing, and scheduling much easier.

Start with one audience and one schedule. Build a template, create a content calendar, and choose a small set of recurring topics that readers expect to see.

Can Hostinger Reach help create real estate newsletters?

Hostinger Reach is an AI email marketing platform that can help you create real estate newsletters for listings, market updates, local events, and client engagement.

Using the AI template builder or pre-built real estate newsletter templates, you can generate newsletter drafts, including new listing emails, neighborhood spotlights, market updates, open house invitations, and newsletters for past clients.

Beyond content creation, Reach includes contact management, audience segmentation, campaign scheduling, and performance tracking tools.

You can monitor opens, clicks, unsubscribes, and recipient engagement to understand which newsletter formats resonate most with your audience.

Those insights can help you refine future campaigns and improve long-term results.

Start with a format that matches your audience, publish on a schedule you can maintain, and refine your approach as you learn what readers value most.

How can I generate leads using email marketing for my real estate business?

Real estate email marketing generates leads when each newsletter gives buyers, sellers, or homeowners a clear reason to respond, request information, or book a consultation.

Market updates can encourage homeowners to request a valuation. New listing emails can drive property inquiries. Buyer education newsletters can lead to consultation requests.

The content attracts attention, but the call to action creates the lead opportunity.

Every newsletter should connect naturally to the next step. Readers who are interested in a neighborhood may want to see available homes. Homeowners reading a market update may want to know how much their property is worth.

Buyers reviewing financing information may want to speak with a lender or discuss their budget.

The closer the call to action aligns with the content, the more likely readers are to engage.

Newsletters work best when paired with a real estate CRM software, a segmented contact list, and a follow-up process.

Real estate lead generation ideas include growing your audience through website forms, property listing pages, open house registrations, downloadable buyer or seller guides, and local market reports.

Once someone joins the list, organized contact management and consistent follow-up help turn newsletter subscribers into conversations, appointments, and future clients.

All of the tutorial content on this website is subject to

Hostinger’s rigorous editorial standards and values.

The author

Ksenija Drobac Ristovic

Ksenija is a digital marketing enthusiast with extensive expertise in content creation and website optimization. Specializing in WordPress, she enjoys writing about the platform’s nuances, from design to functionality, and sharing her insights with others. When she’s not perfecting her trade, you’ll find her on the local basketball court or at home enjoying a crime story. Follow her on LinkedIn.

The post 16 real estate newsletter examples for agents and brokers appeared first on WEBNET Hosting.

If you’ve ever installed a fresh Ubuntu server and spent the next 20 minutes creating users, installing packages, configuring SSH keys, and adjusting networking manually, cloud-init can save yourself a lot of repetitive work.

Cloud-init is the initialization service used by most cloud platforms and virtual machine images. It reads configuration data during the first boot of a Linux system and automatically applies settings like hostname changes, user creation, SSH configuration, package installation, and startup commands.

Ubuntu cloud images already include cloud-init by default, but understanding how it works gives you much better control over automated server deployments. Once you get comfortable with it, spinning up new servers becomes far less repetitive.

What is cloud-init in Ubuntu 26.04?

cloud-init is a Linux initialization service that runs automatically during the very first boot of a new server instance, and its job is to configure the system before you ever log in.

It reads a configuration file called user-data, which contains instructions written in YAML format, and depending on your environment, this file can be provided in several ways:

• Through a cloud provider’s metadata service, such as DigitalOcean, AWS, Azure, or Google Cloud.
• Using a NoCloud datasource for local virtual machines.
• From a seed ISO image in lab or homelab setups.

Once the server starts, cloud-init reads the configuration and begins applying the tasks you defined, such as:

• Creating users
• Adding SSH keys
• Installing packages
• Setting hostnames
• Running startup commands

The cloud-init boot process is divided into five stages:

• Detect – Determines which datasource or platform the server is running on.
• Local – Performs early system setup tasks before networking is available.
• Network – Brings up networking and connects to the datasource.
• Config – Applies most of the configuration modules from your user-data file.
• Final – Runs the last setup tasks, including package installs and custom commands.

By the time the server finishes booting and you can SSH into it, where cloud-init has already completed all these stages and applied your configuration.

One important thing beginners should know is that cloud-init errors are not always obvious. A small YAML formatting mistake or invalid command may cause part of the configuration to fail quietly during boot. The server still starts, but some tasks may never run.

That’s why checking the cloud-init logs should always be your first troubleshooting step after deploying a new instance.

Install cloud-init on Ubuntu 26.04

On official Ubuntu 26.04 cloud images, cloud-init is already installed and enabled by default. However, if you’re using a regular desktop installation, a bare-metal server, or a manually created local VM, you may need to install it yourself.

Start by checking whether cloud-init is already available on your system:

cloud-init --version

Output:

/usr/bin/cloud-init 26.1-0ubuntu2

If you see a version number, cloud-init is already installed and ready to use. If the command returns no output, install cloud-init using the following commands.

sudo apt update 
sudo apt install cloud-init -y

Once the installation finishes, cloud-init is automatically configured and enabled to start during boot.

Check the cloud-init Status

Before creating or testing any configuration, it’s a good idea to verify that cloud-init is working properly on the current system.

cloud-init status

Output:

status: done

Here’s what the different status values mean:

• status: done – cloud-init completed successfully during boot.
• status: running – cloud-init is still processing tasks in the background.
• status: error – Something failed during execution and needs troubleshooting.

If you see an error state, the first thing to check is the cloud-init log files:

sudo less /var/log/cloud-init.log
sudo less /var/log/cloud-init-output.log

These logs contain detailed information about package installations, user creation, YAML parsing errors, and startup commands that may have failed during boot.

For more detailed information, use the extended status command:

cloud-init status --long

Output:

status: done
extended_status: done
boot_status_code: enabled-by-generator
last_update: Thu, 01 Jan 1970 00:00:27 +0000
detail: DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net]
errors: []
recoverable_errors: {}

This output gives you a more detailed breakdown of how cloud-init initialized the system.

One important line here is:

detail: DataSourceNoCloud

This tells you which datasource cloud-init used to retrieve its configuration.

For example:

• DataSourceNoCloud is commonly used for local VMs, lab environments, and ISO-based setups.
• DataSourceEc2 is used on AWS EC2 or DigitalOcean instances.
• DataSourceAzure appears on Microsoft Azure.
• DataSourceOpenStack is commonly used on OpenStack-based clouds.

Knowing the active datasource helps a lot when troubleshooting why a user-data file was or wasn’t detected during boot.

Understand the cloud-init Directory Structure

Before creating your first cloud-init configuration, it helps to understand where the important files and logs are stored on Ubuntu.

Here are the main directories and files you’ll work with most often:

• /etc/cloud/cloud.cfg – the main system config, controls which modules run and in which order.
• /etc/cloud/cloud.cfg.d/ – drop-in config overrides, loaded after cloud.cfg.
• /var/lib/cloud/ – runtime data, including the user-data cloud-init received on first boot.
• /var/log/cloud-init.log – detailed per-module execution log.
• /var/log/cloud-init-output.log – stdout/stderr from every command cloud-init ran.

In most cases, you won’t need to edit /etc/cloud/cloud.cfg directly, because the real configuration work usually happens inside the user-data YAML file you provide when creating the server instance.

You can also inspect the additional configuration files loaded by cloud-init:

ls -l /etc/cloud/cloud.cfg.d/

Output:

total 20
-rw-r--r-- 1 root root 2071 Aug 13  2025 05_logging.cfg
-rw-r--r-- 1 root root  348 May 27 11:54 90_dpkg.cfg
-rw-r--r-- 1 root root   28 May 27 13:16 99-disable-network-config.cfg
-rw-r--r-- 1 root root  167 Aug 13  2025 README
-rw-r--r-- 1 root root   35 May 27 10:30 curtin-preserve-sources.cfg

Some of these files are especially useful to know about:

• 05_logging.cfg – Controls where cloud-init writes its logs.
• 90_dpkg.cfg – Added by Ubuntu’s package system and tells cloud-init to use apt for package management.
• 99-disable-network-config.cfg – Prevents cloud-init from modifying network settings, which is the default behavior on Ubuntu systems that use Netplan to manage networking.
• curtin-preserve-sources.cfg – Helps preserve APT repository settings during installations performed with Curtin, Ubuntu’s automated installer backend.

As you start troubleshooting or customizing cloud-init behavior, these directories become very useful for understanding what happened during boot and why a configuration did or didn’t apply correctly.

Write a User-Data Config File

The user-data file is the heart of cloud-init, where you define everything the server should do automatically during its first boot.

The file must be written in YAML format and the very first line must contain the following header. If it’s missing, cloud-init treats the file as plain text and ignores the configuration completely.

#cloud-config

Now, create a new user-data file:

nano ~/user-data.yaml

Paste the following configuration into the file:

#cloud-config

# Create a new user with sudo access
users:
  - name: tecmint
    groups: sudo
    shell: /bin/bash
    sudo: ['ALL=(ALL) NOPASSWD:ALL']
    ssh_authorized_keys:
      - ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAA <your-public-key>

# Install packages on first boot
packages:
  - vim
  - htop
  - git
  - ufw

package_update: true
package_upgrade: true

# Set the hostname
hostname: tecmint-server

# Write a custom motd
write_files:
  - path: /etc/motd
    content: |
      Welcome to TecMint Server
      Managed by cloud-init on Ubuntu 26.04

# Run commands after packages are installed
runcmd:
  - ufw allow OpenSSH
  - ufw --force enable

Replace <your-public-key> with the actual contents of your public SSH key file.

You can display your public key using:

cat ~/.ssh/id_ed25519.pub

Copy the entire output beginning with ssh-ed25519 and paste it into the YAML file.

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBTvMBRGqRTCCjFEXvmD7TjJkwBpO3X8QZ9vYmK2sNpA ravi@tecmint-server

If you don’t have an ed25519 key yet, generate one first:

ssh-keygen -t ed25519 -C "ravi@tecmint-server"

Then run cat ~/.ssh/id_ed25519.pub again and you’ll have it.

Breaking down the key sections:

• users – creates the tecmint user, adds them to sudo, and injects the SSH key.
• packages – installs vim, htop, git, and ufw via apt.
• package_update: true – runs apt update before installing.
• package_upgrade: true – runs apt upgrade to apply pending security patches.
• hostname – sets the system hostname so you’re not staring at a random cloud-generated name.
• write_files – drops arbitrary file content to any path on the filesystem.
• runcmd – runs shell commands in order, after all other modules finish.

Once this file is ready, you can pass it to a cloud provider or test it locally in a virtual machine using the NoCloud datasource.

Test the Config with cloud-init Schema Validation

Before using your user-data file on a real server, validate it with the built-in cloud-init schema checker, which is important because YAML formatting mistakes are very easy to miss. A single indentation error or invalid key can cause part of your configuration to fail silently during the first boot.

Run the validation command like this:

sudo cloud-init schema --config-file ~/user-data.yaml

If the configuration is valid, you’ll see output similar to this:

Valid cloud-config: /home/ravi/user-data.yaml

If there’s a problem, cloud-init points directly to the invalid section.

Error: cloud-config is not valid:
  - 'users.0.sudo' is not valid under any of the given schemas

This usually means:

• A key name is incorrect
• YAML indentation is broken
• A value format is invalid
• A section is placed in the wrong location

Fix every validation error before deploying the configuration to real systems.

Apply cloud-init Locally with NoCloud Datasource

On a local VM or a homelab server where you don’t have a cloud provider metadata service, you can test your user-data config using the NoCloud datasource, which is the cleanest way to iterate on configs without spinning up real cloud instances.

Create the seed directory structure:

sudo mkdir -p /var/lib/cloud/seed/nocloud-net

Copy your user-data file there:

sudo cp ~/user-data.yaml /var/lib/cloud/seed/nocloud-net/user-data

Create the required meta-data file, which can be empty, but it must exist:

sudo touch /var/lib/cloud/seed/nocloud-net/meta-data

Now clean the existing cloud-init state so it re-runs on the next boot:

sudo cloud-init clean --logs

This wipes the runtime state that tells cloud-init “I already ran on this system“. After this command, cloud-init will treat the next boot as a first boot and reprocess everything.

Important: cloud-init clean removes all state, including user-data that was applied before. On a production system, this triggers a full re-run, which can re-create users, reinstall packages, and overwrite files.

Reboot the machine:

sudo reboot

After the reboot, check the status:

cloud-init status --wait

Output:

.............................status: done

Check the output log to confirm your packages are installed:

sudo cat /var/log/cloud-init-output.log

Output:

Cloud-init v. 26.1-0ubuntu2 running 'init-local' at Fri, 29 May 2026 05:32:28 +0000. Up 3.72 seconds.
Cloud-init v. 26.1-0ubuntu2 running 'init' at Fri, 29 May 2026 05:32:29 +0000. Up 4.06 seconds.
ci-info: +++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++
ci-info: +--------+-------+-----------+-----------+-------+-------------------+
ci-info: | Device |   Up  |  Address  |    Mask   | Scope |     Hw-Address    |
ci-info: +--------+-------+-----------+-----------+-------+-------------------+
ci-info: | enp1s0 | False |     .     |     .     |   .   | 52:54:00:d4:f7:a2 |
ci-info: |   lo   |  True | 127.0.0.1 | 255.0.0.0 |  host |         .         |
ci-info: +--------+-------+-----------+-----------+-------+-------------------+
...
Cloud-init v. 26.1-0ubuntu2 running 'modules:config' at Fri, 29 May 2026 05:32:30 +0000. Up 5.85 seconds.
Cloud-init v. 26.1-0ubuntu2 running 'modules:final' at Fri, 29 May 2026 05:32:32 +0000. Up 7.93 seconds.
...
The following NEW packages will be installed:
  git git-man htop liberror-perl
0 upgraded, 4 newly installed, 0 to remove and 17 not upgraded.
Need to get 5,630 kB of archives.
After this operation, 28.8 MB of additional disk space will be used.
...
Setting up htop (3.4.1-5build2) ...
Setting up git (1:2.53.0-1ubuntu1) ...
Rules updated
Rules updated (v6)
Firewall is active and enabled on system startup
Cloud-init v. 26.1-0ubuntu2 finished at Fri, 29 May 2026 05:32:52 +0000. Datasource DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net].  Up 27.22 seconds

The log shows each package being pulled from the Ubuntu archive (resolute is Ubuntu 26.04’s archive codename), the runcmd entries firing the UFW rules, and finally the finished line confirming everything ran cleanly in 27 seconds.

Pass User-Data Through a Cloud Provider

When launching a real cloud instance, you pass the user-data file at creation time through your provider’s interface or CLI. The process is the same across providers, only the tooling differs.

On DigitalOcean:

In the Droplet creation UI, scroll to the “Advanced Options” section and check “Add Initialization scripts (free)“. Paste the contents of your user-data.yaml directly into the text field.

Using the DigitalOcean CLI (doctl):

doctl compute droplet create tecmint-server 
  --image ubuntu-26-04-x64 
  --size s-1vcpu-1gb 
  --region nyc1 
  --user-data-file ~/user-data.yaml

On AWS (EC2):

aws ec2 run-instances 
  --image-id ami-0abcdef1234567890 
  --instance-type t3.micro 
  --user-data file://~/user-data.yaml 
  --key-name my-keypair

The --user-data file:// prefix tells the AWS CLI to read the file from disk rather than expecting an inline string.

Debug cloud-init Failures

When something goes wrong, the 2 log files tell you everything:

sudo tail -50 /var/log/cloud-init.log

Output:

2026-05-29 05:32:55,321 - stages.py[DEBUG]: Running module package-update-upgrade-install ...
2026-05-29 05:32:55,004 - util.py[WARNING]: Failed to run command: ['apt', 'install', '-y', 'htop']
2026-05-29 05:32:55,005 - util.py[WARNING]: exit code: 100

The WARNING lines show you exactly which module failed and what command it tried to run and the exit code: 100 from apt means the package wasn’t found or the cache was stale, usually fixed by adding package_update: true to your config.

For a fast summary of what ran and what failed:

cloud-init analyze show

The analyze show output gives you a timeline of every module with how long each one took.

Conclusion

cloud-init takes the repetitive first-boot setup off your hands and puts it into a version-controllable YAML file. You covered how to install and verify cloud-init on Ubuntu 26.04, how to write a user-data config that creates users, installs packages, and runs commands, and how to test that config locally using the NoCloud datasource before pushing it to a real cloud instance.

Start with the schema validation step, cloud-init schema --config-file, before you deploy anything. Catching a YAML indentation error locally takes 2 seconds. Catching it after you’ve launched 20 instances takes much longer.

Have you run into a cloud-init issue that wasn’t obvious from the logs? Drop it in the comments and describe what your config was trying to do.

The post cloud-init: How to Set Up Ubuntu 26.04 Servers Automatically appeared first on WEBNET Hosting.