Heating the forge

000%

Connecting

Software foundry by Arfat · Taking on new builds

Raw ideas in. Shipped software out.

ARFORGE is Arfat's studio for web, mobile and backend engineering. One team takes your product from first sketch to production, then keeps it fast.

13 public repositories, 9 deployed live on GitHub

00 What we believe

Most software ships late, breaks quietly and gets forgotten. We build the other kind: on time, hardened in production, and used every single day.

Negative words decay after you read them. Positive words lock in. The sentence does what it says.

01 Services

Three disciplines. One team. Zero handoffs.

01 · Web

Websites that load before you blink.

Marketing sites, SaaS dashboards and storefronts built with React and Next.js. Every page ships against a performance budget, an accessibility check and a real device test.

  • FrameworksNext.js · React · Vue · Astro
  • ContentHeadless CMS, commerce and search
  • CraftWebGL, motion design and 3D
  • GrowthSEO, analytics and Core Web Vitals
02 · Apps

Apps people open without thinking.

iOS, Android and cross platform apps in Flutter and React Native. Offline sync, push notifications, payments and analytics are wired in from the first sprint, not bolted on at the end.

  • Cross platformFlutter · React Native · Expo
  • NativeSwift and Kotlin when it matters
  • DataOffline first sync and push
  • ReleaseApp Store and Play Store delivery
09:415G ▮▮▮

Release 1.0.0

Ready for launch

  • Offline sync
  • Push notifications
  • Payments
  • Crash reporting
Slide to ship

03 · Backend

Backends that stay calm at 3am.

APIs, databases and infrastructure in Node, Python and Go. Postgres, Redis and queues underneath. CI, monitoring and alerts on top, so problems page us before they reach your users.

  • APIsREST, GraphQL and webhooks
  • DataPostgres · Redis · MongoDB
  • PlatformAuth, payments and queues
  • OpsDocker, CI and cloud deploys

arforge@edge: ~/live


        

04 Process

Four strikes from sketch to ship.

Strike 01 · Heat

Discovery

A short sprint to map your users, your risks and the one number that defines success. You leave with a scoped plan and a fixed quote.

Strike 02 · Shape

Design

Flows, wireframes and a clickable prototype, tested with real users before any production code begins.

Strike 03 · Strike

Build

Weekly releases. Every Friday you get a working build, a changelog and a link you can share with your team.

Strike 04 · Temper

Launch

Load tests, monitoring and a hardened release. Then 30 days of post launch care, included in every build.

The real 3D hammer strikes once per milestone. Metal is shaped by repeated blows, and so is software.

05 Work

Selected builds, live from the workshop.

Pulled from GitHub in real time. Every card below is a real repository with a real deployment you can open.

06 Stack

Tools orbit the problem. Never the other way round.

We pick the stack after we understand the product. Drag the sphere, or filter it, and the right tools come forward.

Hover a logo

07 Proof

Claims are cheap.
Here is this page, measured live.

Every number below is read from your browser right now. Nothing on this panel is hardcoded.

0Frames per second
0Milliseconds per frame
0Points drawn this frame
0Draw calls this frame
0Kilobytes shipped to you
0Milliseconds to first strike

Rendering on your GPU

08 Questions

Questions we hear before every build.

How much does a project cost?

Every project gets a fixed quote after a free discovery call. You pay for agreed scope and milestones, never for open ended hours.

How long does a typical build take?

A marketing site usually takes two to four weeks. A web or mobile app with a backend usually takes eight to sixteen. You get a dated plan before any work starts.

Who owns the code?

You do. The repository lives in your GitHub organisation from day one, and full ownership transfers on final payment.

Can you take over an existing codebase?

Yes. We start with a short audit, fix what is risky first, then keep shipping features on top of what you already have.

Do you design as well as build?

Yes. Product design, UI, motion and 3D are done by the same team that writes the code, so nothing gets lost in a handoff.

Which technologies do you use?

Whatever fits the product. Usually React or Next.js on the web, Flutter or React Native on mobile, and Node, Python or Go with Postgres on the backend.

What happens after launch?

Monitoring, bug fixes and performance checks continue for 30 days at no cost. After that you can move to a monthly care plan or take it in house.

Do you work across time zones?

Yes. We overlap at least four hours with your working day and share progress in writing the rest of the time, so nothing waits on a meeting.

Privacy

This site sets no tracking cookies and runs no analytics. The contact form does not send data to any server: it prepares a message on your own device. The work section requests public data from the GitHub API, which sees your IP address like any website you visit. Your time zone is read locally to light the globe and is never sent anywhere.

Terms

Content on this site describes the services of ARFORGE. Project scope, price and timelines are agreed in writing before work begins. Third party assets are used under their licences: Poly Haven models (CC0), Simple Icons (CC0) and NASA imagery (public domain).