Aber Systems

00 IT systems & software

Software, infrastructure and support, engineered as one system.

Aber Systems builds custom web applications and internal tools, sets up the networks, servers and cloud services they depend on, and keeps the whole thing maintained once it is running.

  • custom software
  • IT infrastructure
  • support & maintenance
aber@systems: ~

aber services --list

softwareweb apps · internal tools · integrations & APIs

infrastructurenetworks · servers · cloud · backups · security basics

supporthelpdesk · monitoring · updates

aber project plan --from "your brief"

1 discoverywe map how the work is done today

2 scopea written proposal before anything is built

3 deliverybuilt in stages you can see and test

4 handoverdocumentation, access and a support plan

aber status

ready for your brief

01 Services

Three services that cover the whole system

Most IT trouble starts in the gaps: between the software and the server it runs on, or between the people who built something and the people who have to keep it going. We work on all three parts, so there is no gap for a problem to fall into.

A / software

Custom software development

Web applications, internal tools, and the integrations and APIs that connect the systems you already use.

  • Web applications for staff or customers
  • Internal tools that replace spreadsheets and re-typing
  • Integrations and APIs between existing systems
~/software — custom software development in detail

B / infrastructure

IT infrastructure

The foundations: office networks, servers, cloud setup, backups that have been restored at least once, and sensible security basics.

  • Wired and wireless networks
  • Servers and cloud environments
  • Backups, access control and security basics
~/infrastructure — IT infrastructure in detail

C / support

Support and maintenance

A helpdesk for the people using the systems, monitoring for the machines, and updates applied on a plan instead of by accident.

  • Helpdesk for day-to-day requests
  • Monitoring of servers, services and backups
  • Planned updates with a record of each change
~/support — support and maintenance in detail

02 In practice

What the work looks like, step by step

Pick a service to see a typical run of work. The commands are made up for illustration; the steps behind them describe how each kind of job is approached.

Whichever tab you open, the job ends the same way, with things written down:

  • a scope you approved before work started
  • documentation of what was built or changed
  • the access and credentials for your own systems

# a new internal tool, from brief to handover

aber discover --with "the people who do the work"

→ current process mapped, problems listed, scope agreed in writing

aber build --stage 1

→ first working version on a test address for you to try

aber test --with real-users

→ feedback collected, changes prioritised together with you

aber release && aber handover

→ live system, source code, documentation, administrator access

# getting an office and its cloud services in order

aber audit network servers accounts

→ inventory of devices, services, accounts and who has access to what

aber plan --fix-first risks

→ written plan: what to change, in what order, and why

aber backup configure && aber backup restore --test

→ scheduled backups, plus a restore that has actually been tried

aber document

→ network diagram, credentials handover, recovery notes

# an ordinary support request

aber ticket open "Cannot reach the shared drive"

→ logged with who is affected and what they were trying to do

aber ticket triage

→ priority set by the impact on your work

aber ticket resolve

→ fix applied and confirmed with the person who reported it

aber ticket close --note

→ cause and fix written down, so the same issue is quicker next time

03 Architecture

How the pieces fit together

A simplified drawing of a typical small-business system: people at the top, the software they use in the middle, the infrastructure underneath, and support alongside all of it. Yours will differ — drawing it is one of the first things we do.

Architecture overview: people, software, infrastructure and support Three stacked layers. People and systems: your team, your customers and other systems. Software: internal tools, a web application and integrations. Infrastructure: network, servers and cloud, backups. Software runs on the infrastructure. A support column alongside links the helpdesk to people, updates to the software and monitoring to the infrastructure. PEOPLE + SYSTEMS SOFTWARE INFRASTRUCTURE SUPPORT runs on Your team staff, any device Your customers browser or phone Other systems accounting, CRM, shop Internal tools workflows, records Web application portal, ordering Integrations APIs, data sync Network wired, Wi-Fi, VPN Servers + cloud hosting, storage Backups local + off-site Helpdesk requests from people Updates patches, releases Monitoring health, alerts ONE POINT OF CONTACT ACROSS THE WHOLE DRAWING
Fig. 1 — People, software, infrastructure and support drawn as one system. Scroll sideways to see the whole drawing.

Layer 1

People and systems

Who uses the system and what it has to talk to. Every design decision starts here.

Layer 2

Software

The applications, tools and integrations that carry your processes and your data.

Layer 3

Infrastructure

The network, servers, cloud services and backups the software depends on.

Alongside

Support

Helpdesk, monitoring and updates run across every layer, not just the newest one.

04 Method

How an engagement runs

The same four stages apply whether the job is a new application, a network refit or taking over the support of systems you already have.

  1. Conversation

    You describe the problem in your own words. We ask about the people involved, the tools in use today and what a good outcome would look like.

  2. Written scope

    You receive a proposal stating what will be done, what is not included, what we need from you and how the work is staged.

  3. Staged delivery

    Work is delivered in visible stages. You see and test results as they appear instead of waiting for one big reveal at the end.

  4. Handover and care

    You receive documentation and access to everything built or configured. If you want, we stay on for support and maintenance.

What stays constant

Projects differ; the working rules do not. These four apply to every job, large or small, and they are the things worth holding us to.

Plain language
Proposals, updates and documentation are written so that a non-technical owner can follow them.
Scope first
What is included, what is not, and what we need from you is agreed in writing before work begins.
Visible progress
You can see what is done, what is in progress and what comes next at every stage.
Documented handover
Everything built or configured is written down, and the access to it is handed to you.

05 Next step

Send the brief. Get a plan back.

A few lines are enough to start: what you need built, set up or looked after, who it is for, and what you use today.

aber@systems: ~/contact

mail contact@vatutuexa.site

subjectwhat you need built, set up or looked after

bodywho it is for · what you use today · any deadline

aber next

we reply by email with questions or a time to talk