The Yasa Ecosystem brings websites, hosting, projects, billing, professional opportunities and hardware services into one connected family. Start with the service you need, use your Yasa account where supported, and move between related tools with a clearer sense of where your work belongs.
A website launch makes the idea concrete. You may need a business website, a place to host it, a project space for the team and a way to prepare the invoice. Yasa gives those jobs distinct homes, with connections where they help. You can also use an individual service without adopting the whole collection.
The vision behind the Yasa Ecosystem
Digital work often crosses several boundaries. A brief becomes a project, a project produces a website, and completed work needs a billing record. Meanwhile, people need dependable access, useful guidance and a place to manage their details. The vision behind Yasa is to make those steps easier to navigate through a connected platform.
Each application has a clear purpose. Hercules organises work; Midas handles invoices; Nexus manages assigned infrastructure. Account provides shared identity and settings, while Help explains how the services work. As a result, that division gives teams a practical starting point and keeps responsibility visible as work moves forward.
The benefit comes from useful connections between those responsibilities. For example, selected eligible billable tasks can move from Hercules into Midas for invoice preparation. That saves a handoff while leaving the invoice review with the person responsible for billing. Integration should make the next step clearer and preserve the checks that matter.
Meet the applications in the Yasa Ecosystem
Yasa — websites and digital services. Yasa is the starting point for a new website, an online store or improvements to an existing digital presence. Its services cover WordPress, WooCommerce and Shopify work, alongside support, performance and search optimisation. Start here when you need to discuss the outcome, choose an approach or find a technical partner. Read our Yasa websites and digital services guide for platform choices, delivery and ongoing care.
Nexus — hosting and infrastructure. Nexus brings assigned websites, game servers and infrastructure resources into an administration panel. Access is invitation-only, with Google verification and permissions for the resources you may manage. However, website visitors and game players use their normal public services; they do not need a Nexus administration account. Also, our Yasa Nexus hosting guide explains invitations, environments and recovery.
Hercules — projects and collaboration. Hercules gives project work a home through tasks, subtasks, dependencies, collaborators and useful views. Teams can plan responsibilities, follow progress and prepare billable work. Our existing Hercules projects and Midas billing introduction explains that connection in more detail.
Midas — invoices and billing. Midas keeps customers, products, invoices and payment records together. It supports invoice preparation, PDFs and recurring billing, with review choices for recurring work. Its optional Hercules connection brings eligible selected work into the billing process. However, a completed task still needs the appropriate invoice review; it does not send a bill by itself.
Skills, identity and payments
SkillJobber — skills and opportunities. SkillJobber connects people with projects and professionals with opportunities. Clients can post briefs and compare private quotes. Meanwhile, professionals can browse previews and choose a membership for access to full briefs and quoting within their tier. Personal and permitted company identities come from Yasa Account; professional skills have their own profile.
Account — profiles, settings and security. Account is the shared place for your Yasa identity, personal details, preferences and connected services. It offers Google or email sign-in for supported services. However, each application can still need its own connected session, and company or workspace permissions determine which records and controls you can use.
Yasa Pay — a starting point for payments. Yasa Pay helps you reach the appropriate service and its checkout or billing area. Memberships, shop purchases and other supported payment journeys keep their own context. However, availability differs by service: online invoice payments in Midas are not currently available. Follow the payment link provided for your actual order or membership.
Mail, hardware and help
Webmail — email hosted on Nexus. Webmail provides a browser route to Nexus-hosted email through Roundcube. First, use your Yasa sign-in and then enter the mailbox using its full email address and mailbox password. A Nexus administration invitation is not required to open Webmail. However, you do need an existing hosted mailbox to read or send its messages.
Yasa PC — refurbished computers and components. Yasa PC is the shop for refurbished computers, components and related services. Browse the catalogue, check the individual product details and follow the shop checkout for an order. In addition, connected customers can reach their shop-order view through Account. Product availability, delivery choices and warranty terms belong to the shop and the specific purchase.
PC Builder — hardware, builds and community. PC Builder focuses on hardware inventory, computer builds and the component community. It provides a place to organise hardware information and component choices. Yasa PC serves the shopping journey; PC Builder serves the inventory and build journey. Start with the PC Builder guides to understand the available workflows.
Help — support and practical guidance. Yasa Help brings product guides and common questions together. Browse by service or search for the task you need to complete. In addition, public guides remain available without signing in. If you need further support, include the service, what you tried and what happened so the next conversation can start with useful context.
How work moves between services
Consider a small team preparing a website launch. This example illustrates a sensible sequence; it is not a claim that every step runs automatically. First, the team agrees the website scope with Yasa. It then creates a Hercules project, breaks the work into tasks and gives each task an owner and a clear result.
Next, the people with the appropriate Nexus invitation manage the assigned hosting environment. Content editors and website visitors continue through the website’s own normal experience. For a WordPress site, our WordPress upgrade preparation guide shows why a separate test environment and a checked release remain useful.
When eligible billable work is complete, the responsible person selects it in Hercules and hands it to Midas for invoice preparation. They review the customer, selected work and invoice details before taking the next billing action. Meanwhile, Help provides guidance on the application in use. As a result, each step keeps its owner, purpose and access rules.
SkillJobber can help a team find a professional for a new brief, and the hardware services support a different part of the working day. Those services share the Yasa setting, but a quote, a hardware record or a shop purchase should be managed in the application that owns it. Choose the next tool because it serves the job.
One account, with clear access boundaries
Shared sign-in makes the Yasa Ecosystem easier to enter. It also helps keep personal and company settings together where the service uses them. However, a recognised identity and permission to manage a particular workspace are separate things. Therefore, joining Account does not grant access to another team’s projects, invoices, infrastructure or mailbox.
Nexus makes this distinction especially clear: an invitation and the required verification open the assigned administration resources. Webmail adds the mailbox’s own credentials. Meanwhile, other connected services establish their application session and apply the relevant membership or workspace rules. If a service asks you to connect or sign in again, follow its normal access step.
What an integrated platform adds to everyday work
The practical benefit is a more consistent route through related jobs. Shared account settings reduce repeated profile work where applications use the same identity. Hercules and Midas make a specific project-to-billing handoff available. In addition, product navigation and a common help centre make it easier to find the right destination when your task changes.
Clear boundaries also help teams assign responsibility. A collaborator can work on a project without receiving infrastructure control. A customer can use a public website or shop without becoming a server administrator. Therefore, you can start small, connect the services that help and keep reviewing who needs access as the team develops.
Choose your first step in the Yasa Ecosystem
Begin with the immediate task. For a website or store, discuss the brief with Yasa. Explore Hercules for a team project, or choose Midas for invoice preparation. SkillJobber is the starting point for a professional opportunity. If you need hosting access, arrange the appropriate Nexus invitation rather than assuming a public account includes it.
For the wider picture, use this overview as your map, then follow the relevant product and Help links. The Yasa Ecosystem works best when every tool has a clear job and every connection helps you take a useful next step. Current features and service-specific terms remain available on each application’s own pages.
Talk through your next project
Tell us what you want to build or improve, which services you already use and where the work gets stuck. Contact Yasa to discuss a practical starting point and the services that fit your project.
