Blog

A setup process that does not depend on the company's own environment

The hardware is essentially done; what is left is guiding setup. Most of what gets decided sits on the company's side, not ours.

Engineering Diary › miraiGen.Cube

Our AI server, miraiGen.™Cube, is essentially finished as a piece of equipment; what is left is the work of getting it ready to ship. The hardest part of that has been guiding the customer through setup.

How much a customer can do themselves differs by company

Almost everything decided during installation sits on the company's side, not ours. Can they open the router's settings? Do they own a domain name and run it themselves? Is there anyone who can change DNS — the records that tie a name to a server? Does their internet line come with a static IP address?

Those four questions change enormously how much a customer can do on their own. Work that a company with a knowledgeable person finishes without pausing cannot get past the first setting elsewhere. A carefully written manual does not solve it.

Work stops where the company's environment has to be prepared

Settings inside the server are ours to provide. The time goes before that. Adding a static IP address to an internet line takes anywhere from a few days to two weeks from the application. Routers differ by model and by who administers them, and sometimes the line provider holds them and nobody inside the company can open the settings. Both are a matter of preparing the company's environment, and nothing we do on the product side makes them shorter.

Designing it so adoption is not abandoned

So setup asks one question at a time. Each question carries our recommendation and the reason for it. And anything that cannot be decided yet is explained as something that can be done later, and we move on. We also write down who to approach when that time comes — the line provider, or whoever administers the router. A company that cannot open its router settings still completes every setting inside the server, and picks up where it left off on the day the rest is ready.

In summary

  • The hardest part of adoption is that it depends on the company's own environment. The line contract, the router and DNS cannot be removed by anything we build into the product
  • Write guidance that does not come to a stop. Offer a way of doing it later and the process continues

Even so, there are places where a person helping is simply faster. Resellers can provide that help on site, which is where we are placing our hopes.

← Back to Engineering Diary All posts