How we work
We explain openly how we run a project, how code goes live and how we protect the system after launch. Everything here is something we do today.
$ release 1/5 build (Docker) .......... ✓ 2/5 output checks .......... ✓ 3/5 backup ................. ✓ 4/5 go live ................ ✓ 5/5 live verification ...... ✓ LIVE · search engines notified
At Averis Soft no project is delivered without your approval; code is version-controlled with Git and written in TypeScript. Every release passes automated checks, is preceded by a backup and verified live — and rolls back to the previous version automatically if something goes wrong. Systems we maintain are monitored every 5 minutes and backed up nightly with encryption.
Directly with the developer
Our founder Muhammed Göktuğ Temiz runs your project from analysis to launch. There are no layers in between: the person who listens to your needs is the one who writes the code and monitors the system after launch, so you get fast, technically informed answers.
About usEvery stage moves forward with your approval
- 1Scope
After analysis, deliverables, timeline and price are set out in writing in a scope document.
- 2Design approval
Interface designs are presented for your approval before development starts.
- 3Review before launch
You review the system yourself before launch and give feedback.
- 4Launch approval
No project is delivered without your approval; refinements continue until you sign off.
How does a change go live?
Releases are not done by copying files by hand, but by a script that runs the same steps in the same order every time.
- 01Code and versions
Every change is recorded with Git and stored on GitHub, so what changed and when is always traceable.
- 02Build
The project is built in a Docker environment that gives the same result every time, and passes TypeScript type checks.
- 03Automated checks
Required pages, share images and security settings are checked; if anything is missing, the release stops.
- 04Backup
The live version is backed up and recent versions are kept.
- 05Release and verification
The new version goes live in a single step; key pages, the contact form and security rules are tested live.
If live verification fails, the system rolls back to the previous version automatically. Pages whose content changed are reported to search engines (IndexNow) automatically.
How we protect the system
Uptime monitoring
The site, contact form, SSL certificate and disk are checked every 5 minutes; if a problem persists for two checks an email goes out immediately, and again when it recovers.
Encrypted backups
Data is encrypted with AES-256 every night and copied off the server, with the last 7 days also kept on the server; restore steps are documented.
Security
HTTPS and HSTS, a content security policy (CSP) and security headers, auto-renewed certificates and automatic security updates; secrets are kept outside the web root.
Form and bot protection
Forms use a bot trap and rate limiting; known attack scans are blocked before they reach the application.
Privacy and data protection
Privacy notices, collecting no more data than needed and fixed retention periods; visitor statistics work without cookies.
Measure, then improve
Speed, accessibility and SEO are measured with Lighthouse; changes are checked in a real browser (Playwright) on mobile and desktop.
Monitoring, backups and security updates apply to our own infrastructure and to projects under a maintenance plan.
We practise what we preach on our own site
- 91–94Mobile speed
- 100Desktop speed
- 100Accessibility
- 100SEO
Google Lighthouse, measured October 2026. Mobile is measured with a simulated slow phone and network.
Transify AI: a system that processes heavy jobs without making users wait
In our own product Transify AI, hour-long recordings are processed without keeping the user waiting: every upload is queued, the steps run independently, and the result is announced by email or webhook when ready.
- 1Upload and queue
- 2Speech to text (Whisper)
- 3Translation
- 4AI analysis (separate GPU server)
- 5Output, email and webhook
- Git and GitHub
- TypeScript
- Docker
- nginx
- Let's Encrypt
- AWS
- Playwright
- Lighthouse
- IndexNow
Frequently asked questions
Who develops the project?
Our founder Muhammed Göktuğ Temiz runs your project from analysis to launch; you work directly with the developer.
Does the site go down during a release?
No. The new version is prepared in advance and goes live in a single step; if live verification fails, it rolls back to the previous version automatically.
How do you know if my site goes down?
Systems under a maintenance plan are checked every 5 minutes; if a problem persists for two checks, an email alert goes out immediately.
Where are backups kept?
They are encrypted with AES-256 every night and copied off the server; a copy of the last 7 days is also kept on the server.
Do we own the source code?
Yes. Source code and documentation are handed over at delivery.
Let's bring your next project to life.
Tell us briefly about your project or book an online call; we'll get back to you within 24 hours.