All systems nominal · Payroll cycle closes Jun 30

PhylexPhylex Careers
About

We host things.
We pay people.

Phylex is a small hosting provider with a stubborn opinion about two boring things: infrastructure and payroll. We believe both should be transparent, auditable, and humane — and that there is no good reason for either to be otherwise.

Apply to join See open roles

“We hated being the person to chase our own paycheck. So we built the thing that means nobody on our team ever has to.”

— Phylex founding team, 2024

2024

Phylex Hosting founded

12

Team members today

1,400+

Customer servers under management

99.97%

Uptime last 12 months

/ 01 — Story

How this portal came to exist.

Every growing company arrives at the same Tuesday morning: somebody on Telegram is asking why their payout is late, somebody else can't find the CRM password, and the only spreadsheet that matters has nineteen tabs.

We hit that Tuesday in autumn 2024. By Wednesday we had a list of complaints long enough to be embarrassing. By the end of the month we had decided to build the thing we wished existed.

The result is intentionally small. There is no goal of making this a SaaS. It serves Phylex; it serves the people who work for Phylex; that's it. If someone else copies it, great — we'll send the schema.

What we tried not to copy from the back-office software we'd used: the gatekeeping, the modal-dialog hell, the assumption that “HR” is a different species from the rest of the company. Curators here are engineers. Engineers here approve their teammates' payouts. Everyone reads the ledger.

/ 02 — Values

The handful that actually drive decisions.

Not the full poster-on-the-wall list — the ones we've had to defend, in writing, when somebody (rightly) pushed back.

Default to public
Inside the company, almost everything is readable to almost everyone. The ledger and the audit log are not exceptions.
Pay on the calendar
Payroll closes on a fixed date, settles within a fixed window. The system was built so we don't get to slip.
Make security boring
Boring means cheap to do right. We pick crypto primitives older than us and write the operating procedures down.
Volunteers count
Same dashboard, same chat, same human treatment. Different account flags, but the dignity is identical.
Small is a feature
We will hire when the work demands it, not when revenue says we can. Headcount is not a status symbol.
Talk in writing
Decisions land in the chat with a paper trail. We schedule a meeting after the writing, not before.

/ 03 — Timeline

How we got here.

Short, because we're young. Detailed, because it's ours.

  1. Q3 2024

    Phylex Hosting goes live

    Three founders, two racks, the first paying customer that wasn't a friend.

  2. Q4 2024

    First volunteer joins

    Community moderation kicks off. We realise we have a payroll problem before we even have payroll.

  3. Q1 2025

    First contractor onboarded

    Tech-support engineer. A spreadsheet is born. By April it has nineteen tabs.

  4. Q2 2025

    Phylex Careers begins

    We open the schema editor and start writing this thing — auth, ledger, audit log first.

  5. Q3 2025

    Careers portal in production

    Applications, payouts, internal credits, curated chats — all behind the same login.

  6. today

    12 paid + 8 volunteers

    Median review 23h. Zero missed payroll cycles. The spreadsheet is in a museum.

/ 04 — Money

How we think about money.

Salary moneyis yours the moment it's accrued. You can withdraw it to your bank, your card, or a crypto wallet — whichever rail fits your country and your patience.

Internal moneyis a voluntary holding spot: same currency, no fees, instant. Move salary into internal to pay your own Phylex hosting bills, or to cover a teammate's server. You can always withdraw it back out.

We don't process card payments ourselves and we don't custody crypto on your behalf. Every withdrawal is a manual transfer made by a named finance operator, who attaches the receipt before the request can be closed. The workflow makes shortcuts harder than the right path.

No commingling
Operational and worker funds live in segregated accounts.
Receipt-or-it-didn't-happen
A withdrawal can't be closed without an attached document.

/ 05 — Data

How we think about data.

Card numbers, IBANs, crypto addresses, recovery phrases — these are encrypted with AES-256-GCM before they hit our database. Two independent keys, blast-radius isolated. A database dump without the keys is useless.

Reading any sensitive value, even by an admin, requires a written reason. That reason is part of an immutable audit log. We'd rather make the right thing convenient and the wrong thing visible than ask people to be saints.

AES-256-GCM

Authenticated encryption for all sensitive fields

argon2id

Passwords hashed at OWASP 2024 baseline

Audit log

Append-only; every reveal carries a reason

/ 06 — Team

Twelve people. Five timezones.

We don't do photos here — for the same reasons we encrypt payment data — but the names are real and our chat is open during working hours.

SN

Shafa N.

Founder · Engineering

Wrote the schema. Reviews the audit log.

EK

Eli K.

Finance · Payouts

Processes withdrawals. Will email about receipts.

AR

Aysel R.

Tech Support

First-line, second-line, post-mortems.

DM

Davit M.

Sales

Talks to customers. Closes deals. Reports cleanly.

MK

Murad K.

Content

Tutorials, case studies, docs that don't suck.

LS

Lina S.

Community · Volunteer

Translations. Moderation. Mood.

/ 07 — FAQ

The questions everyone asks.

Open for applications

That's the whole pitch.

Sound like a workplace you'd like to spend time in? Start an application.

Start Browse roles