6 ms·

Hi Everyone: Thanks for the thumbs up on this. Firstly, we are a 20-year old startup! Everyone laughed at us when we talked about doing the original Internet

by mp99e99 12y ago

Hi Everyone: Thanks for the thumbs up on this. Firstly, we are a 20-year old startup! Everyone laughed at us when we talked about doing the original Internet startup -- dialup Internet. Over time, we adapted and rode the booms and busts that went on in our industry, all the while staying cash flow positive and learning to GRIND. We are thinking there is going to be a explosion in startups globally, that will lead to the next big things, not just in the web but material sciences, biotech, etc. Our goal is to build out a global compute infrastructure and get it in the hands of tomorrows Einsteins.. wherever they are born. We want to see the future happen faster, and see more of it in our lifetimes. Thats not going to happen if we wait around for today's dominant players, who for whatever reason are moving extremely slow. Thats our over-reaching goal. You can read about it here: https://www.atlantic.net/blog/2014/09/30/atlantic-net-launches-99-server-go-plan-to-push-the-advancement-of-startup-innovation/ https://www.atlantic.net/blog/2014/09/30/atlantic-net-launch... Doing a startup is really, really hard. We're trying to make it less so. We're also ready to provide an alternative narrative to AWS conquering the world -- but we have to be aggressive and go FAST! So, bottom line is we're trying to do something new,take some risks,be bold, and take on the giants of the industry. AWS's margin is our opportunity :) Wish us luck! We're going for it!

Karunamon 12y ago
This is great to hear, there's nothing ever wrong with more competition, but could you respond to the concerns in this thread with regards to your AUP? Your terms as currently written, are at the very least extremely limiting.
- mp99e99 12y ago
  Hi, I'm going to work on the AUP tomorrow. The spirit of our AUP is to discourage antisocial behavior.
  - ehPReth 12y ago
    Great! Could you reply when the new version is up?
    - mp99e99 12y ago
      We're working on this now, should be up in a few hours.
lsc 12y ago
hey, good luck! this is your day and if your time on hn/reddit was like mine so many years ago when my prices were good, you probably want to be racking up new servers rather than answering questions, but even though I'm a competitor rather than a customer, I imagine others are wanting to know the answers to similar questions: what virtualization technology are you using? Is it openvz/virtuozo/container based? or is it kvm or xen hypervisor based? Are your backups hosted on a different provider or on a different server?
- mp99e99 12y ago
  KVM Backups are on another server in the same datacenter.
  - Morgawr 12y ago
    >Backups are on another server in the same datacenter. You might want to look into moving backups to an offsite location. Datacenter administration 101, if there's a fire or an earthquake or any other natural disaster, you definitely don't want to lose all your data because it was all in the same place. Just a "different machine" doesn't cut it.
    - lsc 12y ago
      >You might want to look into moving backups to an offsite location. Datacenter administration 101, if there's a fire or an earthquake or any other natural disaster, you definitely don't want to lose all your data because it was all in the same place. Just a "different machine" doesn't cut it. You know how often earthquakes happen? fires? You should guard against the common things first. Sysadmin error is a way more common way to lose data than earthquakes or fires. hostile compromise is also a lot more common. Having the data on another server (rather than in a snapshot) is a good first step because it protects you from RAID screwups, and sysadmin error in whatever snapshot layer you use. Generally speaking a reasonable defense against compromise is a reasonable defense against sysadmin error... best practices (and I know of no vps provider, including myself, that actually adheres to these best practices.) are to set up your backups so that the production root can not overwrite or delete old backups. Ideally, no one employee has write access to both production and backups, that way no one person, even if their credentials are compromised by a hostile, or even if they become hostile, can wipe all your data. (note, this requires an off-site backup. Physical access is write access, but this really only protects you from an employee who is willing to risk jail time to hurt you, and while that happens, it's pretty rare compared to an employee's login credentials being compromised. I would setup protection so that no one employee can overwrite both production and backup remotely before spending the effort and money to haul all my backups to another location.) But like I said, as far as I know, nobody actually does that (and its a difficult sort of thing to verify.) - for the low end VPS market? if they have backups on another server (rather than in a snapshot or something on the same server) they are doing okay. But really... if you care? you should do your own backups. As a customer, you don't have any choice about letting your hosting provider have write-access to production. Make sure you have a backup somewhere that they don't have access.
kefka 12y ago
Why the hell do you require a phone# to get this service? What is going on in your ToS? Sure looks lifted from an older provider... And the morality clause with copyright violation of the ToS is rather funny, albeit sad. Why should I pay _you_ money?
- hackerboos 12y ago
  They didn't call me when I signed up. I guess they flag high risk and only call in those cases.
imdsm 12y ago
Want advice? Accept global payments, not just American payments. The internet is global. Want more business? Sort your damn payment structure out. Yes you can have my contact details, I'm not a criminal, but you can FO if you think I'm going to jump through hoops to PAY YOU money. Unless you sort that out, you're stopping people from buying from you, and that my friend, is your biggest mistake.
theshrike79 12y ago
"State" shouldn't be a required field on registration, not every country is the United STATES of America. My country doesn't have states, at least ones that have any kind of influence at any level.
- mp99e99 12y ago
  Interesting, added this to our list of customer suggestions for review. Thanks for the heads up!

by mp99e99 12y ago

Karunamon 12y ago

This is great to hear, there's nothing ever wrong with more competition, but could you respond to the concerns in this thread with regards to your AUP? Your terms as currently written, are at the very least extremely limiting.

mp99e99 12y ago
Hi, I'm going to work on the AUP tomorrow. The spirit of our AUP is to discourage antisocial behavior.
- ehPReth 12y ago
  Great! Could you reply when the new version is up?
  - mp99e99 12y ago
    We're working on this now, should be up in a few hours.

lsc 12y ago

hey, good luck! this is your day and if your time on hn/reddit was like mine so many years ago when my prices were good, you probably want to be racking up new servers rather than answering questions, but even though I'm a competitor rather than a customer, I imagine others are wanting to know the answers to similar questions: what virtualization technology are you using? Is it openvz/virtuozo/container based? or is it kvm or xen hypervisor based? Are your backups hosted on a different provider or on a different server?

mp99e99 12y ago
KVM Backups are on another server in the same datacenter.
- Morgawr 12y ago
  >Backups are on another server in the same datacenter. You might want to look into moving backups to an offsite location. Datacenter administration 101, if there's a fire or an earthquake or any other natural disaster, you definitely don't want to lose all your data because it was all in the same place. Just a "different machine" doesn't cut it.
  - lsc 12y ago
    >You might want to look into moving backups to an offsite location. Datacenter administration 101, if there's a fire or an earthquake or any other natural disaster, you definitely don't want to lose all your data because it was all in the same place. Just a "different machine" doesn't cut it. You know how often earthquakes happen? fires? You should guard against the common things first. Sysadmin error is a way more common way to lose data than earthquakes or fires. hostile compromise is also a lot more common. Having the data on another server (rather than in a snapshot) is a good first step because it protects you from RAID screwups, and sysadmin error in whatever snapshot layer you use. Generally speaking a reasonable defense against compromise is a reasonable defense against sysadmin error... best practices (and I know of no vps provider, including myself, that actually adheres to these best practices.) are to set up your backups so that the production root can not overwrite or delete old backups. Ideally, no one employee has write access to both production and backups, that way no one person, even if their credentials are compromised by a hostile, or even if they become hostile, can wipe all your data. (note, this requires an off-site backup. Physical access is write access, but this really only protects you from an employee who is willing to risk jail time to hurt you, and while that happens, it's pretty rare compared to an employee's login credentials being compromised. I would setup protection so that no one employee can overwrite both production and backup remotely before spending the effort and money to haul all my backups to another location.) But like I said, as far as I know, nobody actually does that (and its a difficult sort of thing to verify.) - for the low end VPS market? if they have backups on another server (rather than in a snapshot or something on the same server) they are doing okay. But really... if you care? you should do your own backups. As a customer, you don't have any choice about letting your hosting provider have write-access to production. Make sure you have a backup somewhere that they don't have access.

kefka 12y ago

Why the hell do you require a phone# to get this service? What is going on in your ToS? Sure looks lifted from an older provider... And the morality clause with copyright violation of the ToS is rather funny, albeit sad. Why should I pay _you_ money?

hackerboos 12y ago
They didn't call me when I signed up. I guess they flag high risk and only call in those cases.

imdsm 12y ago

Want advice? Accept global payments, not just American payments. The internet is global. Want more business? Sort your damn payment structure out. Yes you can have my contact details, I'm not a criminal, but you can FO if you think I'm going to jump through hoops to PAY YOU money. Unless you sort that out, you're stopping people from buying from you, and that my friend, is your biggest mistake.

theshrike79 12y ago

"State" shouldn't be a required field on registration, not every country is the United STATES of America. My country doesn't have states, at least ones that have any kind of influence at any level.

mp99e99 12y ago
Interesting, added this to our list of customer suggestions for review. Thanks for the heads up!