Punfyre Forge
We build complex applications fast, without cutting corners. Forge is our own rapid application development platform. We use it to deliver connected digital solutions from a proven set of in-house modules, with honest, transparent pricing so your budget goes into your product rather than rebuilding the basics.
Select your scope
The platform is structured into applications, each containing modules you can enable. Modules bundle related features and capabilities together. Add-ons extend individual modules with optional extras.
Website Platform
Public-facing marketing site with storefront, checkout, content management, and localisation.
The baseline shell, navigation, and publishing journeys that make Website Platform useful from day one.
Get a professional, fast website up and running immediately.
Included
Optional add-ons
AI assistants for content generation. Uses monthly AI credits.
Scalable session management for customer-facing features.
Granular role-based access controls for administration.
Dedicated pre-production environment for QA and review.
Support Center
Publish structured documentation, guides, reference material, and a searchable help centre.
The baseline shell, navigation, and publishing journeys that make Support Center useful from day one.
Users and teams find answers themselves, reducing support load.
Included
Optional add-ons
AI assistants for help content generation. Uses monthly AI credits.
Staging environment for pre-production QA and client review.
Slide Decks
Dynamic, customer-specific slide decks that can be personalised, tracked, and shared.
The baseline shell, navigation, and core publishing flows that make Slide Decks useful from day one.
Sales teams send personalised decks in minutes, not hours.
Included
Optional add-ons
Deliver decks in multiple locales.
Client Portal
A private, branded workspace where clients track projects, files, invoices, and messages.
Gives signed-in users the workspace navigation, access controls, and account flows needed to use Client Portal day to day.
Clients see everything in one place instead of scattered emails.
Dependencies
- Auth Engine (Server Engine) — will be auto-added
- API Engine (Server Engine) — will be auto-added
Included
Server Engine
The shared backend: API runtime, identity controls, billing, and platform operations.
Delivers the API runtime, identity controls, and platform operations backbone that make Server Engine usable from day one.
Secure, centralised identity management and API backbone for all applications.
Included
Optional add-ons
Server-side locale support for multi-language applications.
Additional database capacity beyond the base allocation.
Managed end-user seat pool for customer-facing applications.
Elevated admin seat pool for back-office operations.
Pre-production environment for API QA and integration testing.
Uptime Monitoring
Status access, incident routing, alert delivery, and data retention for live service operations.
Delivers the status access, incident routing, and notification baseline that make Uptime Monitoring usable from day one.
Know the moment something goes wrong — before your users do.
Included
Optional add-ons
AI-assisted incident triage and anomaly detection.
Pre-production monitoring environment for test scenarios.
Dev Toolkit
Connect external website analytics to improve conversion tracking and reduce compliance risk across the platform.
Enables marketing teams to manage external integrations safely, driving commercial growth and ensuring faster onboarding for new tracking requirements across the platform.
Connect external website analytics to improve conversion tracking and reduce compliance risk.
Included
Optional add-ons
Matching Figma components for designers.
Localisation support in the component library.
Pre-production environment for component and integration QA.
Mobile App
Native or cross-platform mobile app. Mostly billed on an hourly basis.
Cross-platform mobile app with your branding.
Reach users on iOS and Android from one codebase.
Dependencies
- API Engine (Server Engine) — will be auto-added
Included
Optional add-ons
Face ID and fingerprint login.
Links open specific screens in the app.
Hosting & extras
Hosting costs are determined by several factors including your active applications, their chosen add-ons, traffic volume, and data complexity. Items marked "Included" or "Always on" come at no extra cost. Everything else shows its monthly price clearly.
Environments & scaling
Production instances and staging environments. Instance pricing scales with total system runtime load based on your selected applications and bundles.
Always-on production instances serving live traffic. Priced per instance, scaling with total system runtime load. At least 1 is required.
Total: 1 instances / month(1 instances included free)
€ 0/month per extra instance
AI credits
Monthly AI token capacity for generation and workflow automation. Each pack adds 5K tokens. Pricing scales with total system runtime load.
Adds token capacity for AI-assisted generation and workflow automation. 5 packs of 5K tokens included per month.
Total: 5 × 5K tokens / month(5 × 5K tokens included free)
€ 0/month per extra 5K token
Storage
Database storage capacity for persisted application data. Each block adds 10 GB. Pricing scales with the number of data bundles in scope.
Adds database storage capacity for persisted application data. 1 block of 10 GB included. Price scales with the number of data-heavy bundles in scope.
Total: 1 × 10 GB / month(1 × 10 GB included free)
€ 2/month per extra 10 GB
Users & access
End-user and privileged seat capacity. Seat pricing scales with total system runtime load.
Customer-facing or member-facing access. 250 seats included; add more in blocks of 50. Price scales with system runtime load.
Total: 250 seats / month(5 × 50 seats included free)
€ 0/month per 50 extra seats
Localization
Additional language support across your applications. Pricing scales with the number of localized bundles in scope.
Additional language support for content and interfaces. 1 language included; pricing scales with the number of localized bundles in scope.
Total: 1 languages / month(1 languages included free)
€ 6/month per extra language
Select packs to populate this view
Use the application tabs above to choose your capabilities
Continue the conversation
Fill in your details and click send. Your mail client will open with the full estimate summary pre-filled. Indicative total: € 0/month.
Our in-house modules
Every application we build through Forge draws from the same set of in-house modules: auth, APIs, data management, and hosting. Built and maintained by us, they keep quality consistent across every project. Each application you add connects to what is already there rather than duplicating it.
Shared foundation
Every application sits on top of the same infrastructure layer. Click any block to jump to its details below.
Application catalogue
A closer look at what each one does, who reaches for it, and what real projects look like.
Website Platform
Pages, blog, login, payments
A public-facing website with the essentials built in: responsive pages, SEO, performance, and security. You can add a blog, user login, e-commerce, a page editor for your team, and more. It runs on the same infrastructure as every other Forge application, so adding a client portal or mobile app later does not mean starting a separate project.
Typical use cases
- A consultancy capturing leads alongside their blog and case studies
- A SaaS team whose marketing site flows directly into their client portal
- A non-technical team updating pages and posts without developer help
Example projects
Support Center
Guides, reference, search
A structured knowledge base where your team publishes guides, reference material, and how-to articles. Customers find answers on their own, which reduces incoming support volume and frees your team for higher-value conversations. AI-powered search suggests relevant answers as users type, and version switching lets you maintain docs for multiple product releases at once.
Typical use cases
- A software product with release notes, API docs, and onboarding in one place
- An ops team whose internal runbooks new hires can search on day one
- A service business that cut support tickets by publishing clear help articles
Example projects
Slide Decks
Custom, trackable decks
Dynamic slide decks your team builds once and personalizes per customer. The platform auto-inserts customer names, logos, and data into each deck, and every share link tracks how long recipients spend on each slide. Sales teams stop recreating the same presentation from scratch and start knowing which content actually lands.
Typical use cases
- A sales team whose proposals auto-fill with customer name, logo, and pricing
- An agency that sends each client a deck showing their campaign results
- A product team whose onboarding slides stay current as the product evolves
Example projects
Client Portal
Portal for end clients
A private, branded space where each client logs in to see their project, files, invoices, and messages. It replaces scattered email threads and shared folders with one clear view of everything happening. Because it runs on the same auth and API layer as your other applications, it connects directly to your existing data.
Typical use cases
- A law firm where every client sees their own matter, docs, and invoices
- An agency whose clients log in to review deliverables and sign off on work
- A SaaS company letting customers track usage and tickets without emailing support
Example projects
Uptime Monitoring
Status, incidents, alerts
Real-time uptime checks, incident routing, and alert delivery for live services. When something goes down, the right person is notified through the right channel within seconds. A branded public status page keeps subscribers informed during incidents, and retained incident history gives your team the data for post-mortems and compliance audits.
Typical use cases
- A SaaS team that needs to know about outages before customers start emailing
- An ops team routing critical alerts to on-call engineers via Slack and PagerDuty
- A service business providing clients with a public status page and incident updates
Example projects
Server Engine
Auth, API, infrastructure
The shared backend that powers every application in the ecosystem. It handles authentication across all your apps, exposes a clean API layer for your data, and runs on managed cloud infrastructure with monitoring and CI/CD already configured. Most clients never select this directly as it gets pulled in automatically when other applications need it.
Typical use cases
- A platform where one login works across the website, portal, and mobile app
- A team sharing data securely via API between their product and a third-party partner
- A business with multiple front-ends all reading from the same database
Example projects
Mobile App
iOS and Android app
A cross-platform mobile app built on the same API and auth layer as the rest of your platform. One codebase covers both iOS and Android, and we handle submission to the App Store and Google Play. It supports push notifications, offline use, and biometric login, and connects directly to your existing data without a separate backend.
Typical use cases
- A field team whose mobile app syncs with the office system in real time
- A membership club where users book, pay, and manage their account from their phone
- A web platform that added iOS and Android support without a separate codebase
Example projects
Dev Toolkit
Components and tooling
A component library and developer tooling suite built on the same design system as the rest of the ecosystem. If your team wants to build custom features on top of Forge, this gives you the foundation: tested UI components, a theme system, CLI generators, and linting. It is also available as a standalone kit for teams building outside of Forge.
Typical use cases
- An in-house team building custom features on top of Forge with the shared component library
- A design team keeping brand consistent across products using the Figma kit and token system
- An agency standardizing their delivery stack across every client project
Example projects
How hours translate to cost
Every module is scored across three engineering dimensions (Scope, Depth, and Footprint), each rated on a five-point scale from Standard to Complex. Those scores determine the days estimated for each module, which drive both the integration fee and the ongoing monthly hosting cost.
Estimation dimensions
These appear as colored dots next to each module. They rate each module across three dimensions on a five-point scale.
Scope
How much functionality is included: screens, logic, data, and features. A wider scope means more code to build, review, and maintain.
Depth
Engineering rigor underneath the surface: tests, error handling, security, and compliance. Higher depth reflects more thorough, resilient engineering.
Footprint
How much of the platform this bundle touches: shared data, connected services, and cross-application dependencies that increase coordination cost.
Complexity bands
Five complexity bands that anchor how modules are priced. The dimension bars cycle through valid combinations within each band, illustrating that minor differences in scope, depth, or footprint can exist without shifting the overall cost category.
Standard
Small focused bundle with a handful of screens, straightforward logic, and minimal integrations.
€8–€16/mo
Moderate
Mid-size feature with some backend work and a couple of external connections.
€18–€32/mo
Extended
Multi-screen module with solid test coverage and several shared data models.
€35–€58/mo
Advanced
Complex feature set touching many platform parts, with deep security requirements.
€62–€95/mo
Complex
Full-featured bundle with advanced automation, real-time systems, and compliance requirements.
€100–€180/mo
What you see is a fraction of what goes in
Every module represents a curated slice of work. The estimate shows engineering time. It does not show the architecture decisions, the hardening, or the edge cases compressed into each one.
System-level indicators
These aggregate signals reflect the overall impact of the selected configuration across all applications and modules. Each one rolls up lower-level metrics to give a sense of where complexity, effort, and cost are concentrated.
Module-level indicators
Per-module signals that appear as coloured dots on each capability module. They show the relative scope, engineering depth, and platform footprint of that individual module.
Raw engineering metrics
The underlying data points that feed into the indicators above. These are never shown directly in the estimator but are used internally to calculate each indicator score.
How we work
Six engineering principles that compound over time. The more projects we complete, the more efficient the next one becomes.
Reusable by default
Write once, deploy everywhere
Every component, hook, and utility is a reusable module from day one. Bug fixes propagate everywhere, new features build on proven foundations that have been validated in production.
Modular architecture
Swap, scale, or extend any part
Systems are composable modules with clear boundaries. Each module owns its data, logic, and UI. Add, remove, or upgrade any part without touching the rest. Maintenance stays linear as the system grows.
Stability over novelty
Proven tools, predictable results
Boring, well-understood technology over the latest trend. Every dependency is evaluated for long-term maintenance cost and community health. Your platform runs on tested foundations.
Performance as a feature
Fast by architecture, not afterthought
Static generation, edge caching, code splitting, lazy loading, and optimised queries are part of the default setup. Sub-second page loads and green Core Web Vitals out of the box.
Automated quality gates
Catch problems before production
Every commit runs through automated tests, type checking, linting, and build verification. Regressions are caught in minutes, not discovered by users. We deploy confidently and frequently.
Pragmatic to the core
Maximum output, minimum complexity
If something can be generated, we generate it. If a pattern repeats, we abstract it. If a step can be automated, we automate it. Less code means fewer bugs and lower costs; savings passed to you.
Cost + 15% margin
We price everything at actual engineering cost plus a constant 15% margin, and that never changes. Longer commitments let us negotiate cheaper infrastructure contracts, which lowers our cost basis and passes real savings to you. This page explains our rates, how they compare to the market, and how commitment discounts work.
Where we sit in the market
Hourly rate comparison for fullstack development. Our costs land at the bottom of the scale while delivering quality from the top. Here is why that is not a contradiction.
Offshore teams or freelancers. Low hourly rates but often higher total cost due to rework, communication overhead, and quality gaps.
Small teams with lower overhead. Good for simple projects, but limited scalability and often lack structured processes or testing.
Enterprise-grade reusable systems, priced at actual engineering cost + 15% margin. Years of compounding investment keep costs low while quality stays at the top.
Established agencies with proven processes. Solid quality but higher overhead from larger teams, office costs, and account management layers.
Large consultancies with extensive processes, compliance certifications, and large teams. Premium pricing for brand assurance.
Why this works
Low cost is a result of high quality, not a trade-off against it.
Compounding efficiency
Every project adds to our shared library of battle-tested components and utilities. Each one is faster and more reliable than the last.
Constant 15% margin
Our margin is always 15%. It never goes higher, even on complex work. When you commit to a longer term, we negotiate cheaper hosting contracts, driving the cost basis down. The discount you see is real infrastructure savings, not a margin cut.
Pragmatic laziness
If something can be generated, we generate it. If a pattern repeats, we abstract it. Less code means fewer bugs and lower costs; savings passed to you.
How we keep costs low
Six engineering principles that compound over time.
Reusable by default
Write once, deploy everywhere
Modular architecture
Swap, scale, or extend any part
Stability over novelty
Proven tools, predictable results
Performance as a feature
Fast by architecture, not afterthought
Automated quality gates
Catch problems before production
Pragmatic to the core
Maximum output, minimum complexity
Commitment discounts
Our margin is always 15% and never changes. When you commit to a longer period we can negotiate better infrastructure contracts, which lowers our actual cost basis. Since the margin stays constant, the savings pass directly to you. All plans are billed monthly with no upfront payment required.
1 year
Default12-month commitment, billed monthly.
2 years
24-month commitment, billed monthly.
3 years
36-month commitment, billed monthly.
Fair terms
The 15% buffer
Bar width shows total cost of delivery. Taking on more in-house lowers the invoice, but every team faces a learning curve on a new system. We already know every corner of ours.
We do the heavy lifting, your team learns along the way with minimal overhead.
Your team does most work, we review and guide. Coordination overhead increases significantly.
Your team handles it all, we're available for questions. Maximum learning curve and coordination costs.
Even the best team needs time to learn a new system. We can only predict what is on our end. The rest depends on your environment, existing integrations, and how quickly your team gets up to speed. The buffer exists so discoveries along the way are covered without extra charges.
Build your estimate in the Project planner
Select modules to generate a personalised review