<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: kalikpro</title>
    <description>The latest articles on DEV Community by kalikpro (@__b85bde347).</description>
    <link>https://dev.to/__b85bde347</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4131924%2Fb3227469-99cb-4701-8381-e9172a1d059d.png</url>
      <title>DEV Community: kalikpro</title>
      <link>https://dev.to/__b85bde347</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/__b85bde347"/>
    <language>en</language>
    <item>
      <title>I Built a Telegram-Based Hosting Service. Now I Need to Find My First 50 Customers.</title>
      <dc:creator>kalikpro</dc:creator>
      <pubDate>Mon, 21 Sep 2026 18:55:48 +0000</pubDate>
      <link>https://dev.to/__b85bde347/i-built-a-telegram-based-hosting-service-now-i-need-to-find-my-first-50-customers-4nai</link>
      <guid>https://dev.to/__b85bde347/i-built-a-telegram-based-hosting-service-now-i-need-to-find-my-first-50-customers-4nai</guid>
      <description>&lt;p&gt;I didn't start SyndiHost because I wanted to build another hosting company.&lt;/p&gt;

&lt;p&gt;I started it because I wanted to simplify a process that kept feeling more complicated than it should.&lt;/p&gt;

&lt;p&gt;Hosting a website often means dealing with several separate things:&lt;/p&gt;

&lt;p&gt;hosting;&lt;br&gt;
files;&lt;br&gt;
domains;&lt;br&gt;
DNS;&lt;br&gt;
SSL;&lt;br&gt;
migration.&lt;/p&gt;

&lt;p&gt;If you have one website, that's manageable.&lt;/p&gt;

&lt;p&gt;If you work with multiple websites, the routine becomes much more noticeable.&lt;/p&gt;

&lt;p&gt;My idea&lt;/p&gt;

&lt;p&gt;I decided to put the user interface inside Telegram.&lt;/p&gt;

&lt;p&gt;The concept:&lt;/p&gt;

&lt;p&gt;User&lt;br&gt;
 ↓&lt;br&gt;
Telegram bot&lt;br&gt;
 ↓&lt;br&gt;
Backend&lt;br&gt;
 ↓&lt;br&gt;
Hosting infrastructure&lt;/p&gt;

&lt;p&gt;The bot handles the user interaction while the backend handles the actual work.&lt;/p&gt;

&lt;p&gt;One of the main features: copying websites&lt;/p&gt;

&lt;p&gt;I wanted users to be able to take a ready website and prepare it for hosting without going through a long manual process.&lt;/p&gt;

&lt;p&gt;Because copying can take time, I built a queue for longer operations.&lt;/p&gt;

&lt;p&gt;The flow is roughly:&lt;/p&gt;

&lt;p&gt;User starts task&lt;br&gt;
       ↓&lt;br&gt;
Task enters queue&lt;br&gt;
       ↓&lt;br&gt;
Server processes it&lt;br&gt;
       ↓&lt;br&gt;
Result is returned&lt;br&gt;
The product&lt;/p&gt;

&lt;p&gt;SyndiHost currently combines website hosting and website copying in one Telegram-based workflow.&lt;/p&gt;

&lt;p&gt;Hosting starts at 49 RUB/month.&lt;/p&gt;

&lt;p&gt;The core promise is intentionally simple:&lt;/p&gt;

&lt;p&gt;Copy → host → done.&lt;/p&gt;

&lt;p&gt;Now comes the hard part&lt;/p&gt;

&lt;p&gt;The product is working.&lt;/p&gt;

&lt;p&gt;Now I need to find out whether people actually want it.&lt;/p&gt;

&lt;p&gt;My first milestone is:&lt;/p&gt;

&lt;p&gt;50 paying users.&lt;/p&gt;

&lt;p&gt;Then:&lt;/p&gt;

&lt;p&gt;100 → 300 → 500.&lt;/p&gt;

&lt;p&gt;I'm planning to test content, communities, search traffic, direct outreach and other acquisition channels rather than assuming I already know what works.&lt;/p&gt;

&lt;p&gt;If you're interested in the experiment, the project is here:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://t.me/SyndiHost_bot" rel="noopener noreferrer"&gt;https://t.me/SyndiHost_bot&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I'd also be interested in hearing how you currently handle website migration and hosting.&lt;/p&gt;

</description>
      <category>buildinpublic</category>
      <category>saas</category>
      <category>sideprojects</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
