Get in Touch
Reach us Directly
Answers Before You Reach Out
It reaches the WECORE team directly and we reply within 24 hours. The first reply is usually a short set of questions about the workload and where it needs to run, because those two answers shape almost everything after them. If you would rather start by talking, the number is +98 (21) 82802264.
The workload you want to run — simulation, HPC, GPU training or inference, virtual machines, Kubernetes, cloud desktops — a rough sense of its scale, and whether it should run on infrastructure you own or on WECORE Hub. A timeline and any constraint on where the data may reside will save a round trip.
No. Choosing between them is part of the conversation. WECORE runs three ways: On-Premise, deployed and operated on infrastructure you own or lease; joined to WECORE Hub, which turns your capacity into a sellable, billable product; or hybrid, keeping your own infrastructure and bursting to Hub capacity at peak. The stack underneath is the same OpenStack and Ceph in all three — what changes is where it runs and who owns it.
Not yet. A self-service, hourly public cloud is on the roadmap rather than the current offer, so there is no online checkout to click through: this form and the phone number above are the way in. Once an environment is running, your team works in the WECORE panel, which can be presented under your own organization’s brand.
A range, yes; a firm number comes after sizing. An estimate is built from the deployment model, the size of the infrastructure in nodes, cores and memory, the number and type of GPUs, storage and network, and the level of support. Tell us the workload and we will size it and prepare a tailored quote, rather than quote a tariff we would have to walk back.
The same team you are writing to. Two things are worth knowing before you ask: isolation and traffic control here are software-defined — Neutron security groups, and network functions delivered as VNFs through OpenStack Tacker rather than as hardware appliances — and replication between Ceph clusters is something we configure deliberately, with RBD mirroring or RGW multisite, not something that happens by default. Send the specific requirement and you will get a straight answer on what the stack does and does not do.