Brief
You describe the users, the job to be done, current tools and any hard date or constraint. A page is enough.
Technologies
MySQL as a designed database, not a dumping ground for models
Hirvex Technologies designs and operates MySQL (and MariaDB-compatible) databases for the applications we build. Indexes, migrations and backup restore tests are part of engineering. We do not “just let Eloquent create tables” on a production instinct.
Who this is for. Teams whose application is slow, inconsistent, or one restore-test away from a surprise.
Problems we typically meet
These are the patterns that show up before a useful first release—not abstract “digital transformation” language.
- N+1 queries were discovered by users, not by logs.
- There are no foreign keys “for flexibility”.
- Backups have never been restored.
- JSON columns hide a second schema.
How we approach the work
Model the documents and invariants. Migrations are reviewed. We measure slow queries. JSON is used with intent, not as a junk drawer.
What a serious first release can include
Scope is confirmed in discovery. This is the shape of work we are equipped to deliver—not a menu you must buy in full.
- Schema design
- Migration discipline
- Query and index work
- Backup and restore planning
- Laravel and SQL pairing
What we need from you
A useful brief is better than a long one. If you can answer most of the following, we can propose a first slice instead of a theatre estimate.
- Who will use this, and what must they finish in a session?
- Which systems must stay (accounting, payments, identity, a shop)?
- What is already live that we should not break?
- Any hosting region, language or compliance rule that is non-negotiable?
- The date that actually matters—and why.
How an engagement runs
Four steps. No mystery bench.
Scope
We reply with clarifying questions and a first-release outline: modules, roles, integrations and what “done” means.
Build
Named engineers work in visible increments, with staging you can click and a weekly written status.
Run
Launch, handover and a support path. The system is yours to operate—not a black box we disappear from.
Questions we are asked
MySQL or PostgreSQL?
Both are in our database set. PostgreSQL is often preferable for heavier integrity and JSON/relational mix. MySQL remains an excellent default in many Laravel hosting environments. We pick with operations in mind.
Do you provide database administration as a 24/7 DBA shop?
No. We engineer and maintain the databases of systems we run. Dedicated DBA retainers are a different service class.
Start a conversation
If this is the work in front of you
Send the users, the job to be done and any hard constraint. We will answer as engineers—not with a canned brochure.