I created my own VPS providing service, what do you think?

I created my own VPS providing service, what do you think?

Before I start with all details, I'll like to say that this is project from fun, not expecting too much from it, actually expecting nothing from it, but I wanna see how it would play out. Honestly, from age I became aware of myself, I wanted to do this, so finally took courage and some ca$h to start it. Please don't be too rude and too judgy :P. Just give me some pointers and/or tips.

I've created my own VPS hosting provider app from very start. It took me some time to develop this and make it fully functional. I wanted it to be as simple as possible on design, but on functionality, fully advanced.

(Little background on me) I'm developer, making simple web apps (mostly to control bots I create), automation bots and scrapers. Honestly, I love Linux so much that I feel like I might explode with from one, and always admire how servers are sold, how they are managed and how one VPS can be created and sold at same time LOL. I spent too much time learning about this (proxmox, python API, dedicated server) and finally decided to take a step in and start with it. Took bigger and powerful dedicated server which can handle lot of VMs at same time (if you wish to know about specs, I can share them), rented IPv4 /24 subnet from some provider (not yet on own ASN, but soon when I get one :D).

(Now something about app itself) Like said, design is as simple as possible, bootstrap 5.3, some icons, anime logo and... well that's it. Backend is a bit more advance from frontend. System is automated (fully made by me), so when order is placed, it would check if its paid, if so it would provision VPS and email to user, put data in DB, show in frontend and thats it. Also created fully functional ticket system, to create ticket (admin and user), reply, close and delete (actions for admin only). Cloudflare turnstile implemented for registration and tickets itself. Praying to be good enough for bots and *** LOL. There is referal system which would automatically track and display every single user signed with url code, count % of sale to that user. It's automated and tested, it works!!!! Payments are done via cryptocurrency (BTC only) with some crypto payment processor, which offers API to automate it.

(All in all) It's not much and as said I don't expect too much from it. But it's my own first bigger project on something I always wanted to start. I know there is lot of handle, still I own dedicated server which can handle lot of VMs at same time as said, but IPs are rental. TODO is to get own ASN and buy own IPs. So it's saying [BUSINESS_NAME] on iplookup, awawawaw! It would be so cute. But for start seems to be fine. Just FYI, I didn't use ChatGPT at any time, f* that. I paid to some peps to create me texts.

For now; customers are mostly people I work with, cause marketing is not my good side. Still looking for some things on how to promote it better and efficient.

NOTE: I would not share link publicly for now, maybe would be putting in comments if some wants to see it. But mostly I would like to know if you would recommend something, some tips / tricks (no magic ones pls).

Discussion 0 comments · 1 points · someonefrom80s · 2025-04-01
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.