Welcome to Prometheus Unleashed

Prometheus is the IT Product and Services wing of AmadeusWeb and part of the Dynamic AmadeusWeb Network (DAWN). I built it to help organisations establish capable digital homes, connect with others on their own terms, protect their work, and operate the systems that turn good intentions into dependable services.

My conviction is straightforward: technology should increase an organisation's ability to act, not make it dependent on opaque platforms, proprietary silos, or systems it cannot understand. A website and its supporting tools should be useful, maintainable, portable, and aligned with the organisation's mission.

Prometheus brings together product thinking, hands-on engineering, and team enablement. I work with you to understand the mission and requirements, shape a practical architecture, build or connect the needed capabilities, and help your team take lasting ownership of the result.

I am Imran Ali Namazi, founder of AmadeusWeb and lead technologist at Prometheus. I welcome you — whether you are a prospective client, a member of your team, an end user, an ecosystem partner, or simply exploring what a more intentional internet could make possible.

A technologist's perspective, earned over 26 years

I have spent 26 years building systems across a wide range of contexts — from hobbyist electronics and software to enterprise applications, global products, and frameworks used by teams.

I learned BASIC on a Spectrum at eleven. At fourteen, I encountered WordStar and paper-based ERP through a family business. I went on to co-design electronics projects, build Windows applications, and graduate in Electronics Engineering.

My professional work has taken me through web products, ERP, loan application and servicing systems, financial and HR/legal applications, reporting frameworks, mobile platforms, internal tools, and business workflows.

At Photon, I helped rebuild worldwide sales pages and build community capabilities for Englishtown, a global English-learning product. At Applied Development, I worked across ERP frameworks, object-relational mappers, service management, financial systems, and internal tools. At Headstream, I led engineering and delivered implementations through a period of transition. At Sulekha, I worked on architecture and infrastructure for a mobile consumer-to-service-provider platform and proved the concept of a scalable communications centre integrating external providers.

I have also worked across .NET, C#, PHP, JavaScript, VueJS, TypeScript, ASP.NET Core, SQL Server, and custom frameworks. I have built reporting engines, migration and code-analysis tools, application frameworks, and the AmadeusWeb Spring platform itself.

This breadth gives me practical engineering judgment. I know when a simple architecture removes needless burden, when an organisation needs a more robust integration, and when the right answer is to use a specialist tool rather than reinvent it. I bring that judgment directly to Prometheus projects.

The four-step Prometheus product vertical

Prometheus guides organisations through four connected stages: Marketing, Federation, Security, and CRM / ERP. Each stage addresses a different need, but together they form a continuous digital capability — from being understood by the right people to delivering and improving the work.

1. Marketing: a clear mission and an owned digital home

I help you express who you are, what you offer, whom you serve, and how people can take the next meaningful step.

Your website becomes the canonical home for your pages, articles, events, services, and resources. Campaigns and social channels can lead people back to information you control, rather than becoming the only place your work exists.

We structure your message around your audiences and real offers. We make contact details, service terms, authorship, and calls to action easy to find. We focus measurement on useful outcomes — such as relevant enquiries and completed actions — rather than intrusive surveillance or attention-maximising engagement.

The result is marketing that builds understanding and trust while strengthening your long-term ownership of your public presence.

2. Federation: connect without giving up independence

Through DAWN, I help connect independent organisations and missions while preserving each member's domain, identity, content, local policies, and governance.

Federation can support shared discovery, directories, public profiles, events, service listings, referrals, and initiatives. The goal is to make collaboration easier without forcing every member into a single portal or a central store of everyone’s information.

Each organisation should have control over what it publishes and shares. Shared information should retain its source and context. Participation should be voluntary, and a member should be able to change its connections or leave the federation without losing its website or content.

I approach federation as both a technical and a human responsibility: systems must interoperate, and the relationships between participating organisations must remain clear.

3. Security: reduce unnecessary risk through thoughtful design

I treat security as part of the architecture and the operating practice, not as a feature added at the end.

AmadeusWeb Spring uses file-based publishing for public site content. For sites that do not need database-backed publishing or public administrative logins, this can remove those components — and their associated maintenance and exposure — from the design.

Git provides revision history and a practical route to review and recovery. Teams can work offline, inspect changes locally, and publish after review. Access to hosting and administrative credentials can be separated from routine content editing.

Security still depends on the full operating context. Private records, authenticated features, integrations, backups, and hosting each require appropriate controls. I help identify those requirements, minimise the information collected, establish safe access and recovery practices, and choose safeguards proportionate to the risks.

The aim is not a careless promise that any system is invulnerable. It is an understandable, maintainable system with fewer unnecessary moving parts and explicit responsibility for the parts that remain.

4. CRM / ERP: connect relationships to delivery

I help connect the public journey with the operational work behind it.

An enquiry can become a consented contact, a conversation can become an agreement, and an agreement can become a project, service task, or delivery schedule. Clear ownership, follow-up, and records help ensure that commitments are not lost between marketing and operations.

The appropriate solution depends on the organisation. It may begin with a lightweight enquiry register, contact pipeline, follow-up reminders, and project tracker. It can grow through custom workflows and integrations with specialist CRM, accounting, payment, email, or scheduling tools.

Customer and operational records should remain scoped to the organisation that collected them. Sharing with another member should be intentional and limited to the information needed for a specific purpose.

My experience building ERP frameworks, loan servicing systems, reporting tools, communications capabilities, and business workflows helps me design this stage around actual work — not just a list of software features.

AmadeusWeb Spring: a foundation with room to build

The technology foundation for Prometheus and DAWN is AmadeusWeb Spring v9.9. It is a mature, proprietary framework shaped by years of development and my wider experience building software and frameworks.

Spring combines ordinary web technologies with a framework that connects the pieces into complete sites. It supports content and components in Markdown, HTML, PHP, TSV sheets, forms, presentation decks, and media. Pages can carry their own metadata, while folder structures can define sections, pages, and contextual navigation.

This file-based approach keeps content visible and workable with familiar tools. Teams can develop locally, review changes before publishing, and use Git to track and recover revisions. Shared or large media can be served from a CDN so that individual site repositories remain focused. Where public transparency is appropriate, repositories can also make a site's structure and changes inspectable.

Spring is not a claim that one framework already contains every specialised business application. It is a flexible foundation and a substantial set of building blocks. I use it to meet a wide range of web, publishing, and workflow requirements; where a need calls for more, I assess the right custom extension, integration, infrastructure, or specialist product.

That is how I approach the “world of possibilities”: understand the need first, then select and combine the simplest sound tools to meet it.

Building capability, not dependency

I do not want your team to be locked out of its own digital presence. I train people to work with their own content and tools, understand the architecture, and take part in maintaining and extending the system.

Depending on the project, that can include practical work with VS Code, TortoiseGit, Markdown, folder-based content organisation, project planning, documentation, review, and publishing workflows.

The development process can be offline-first: your team can prepare and review changes locally before they are published. Work can be organised as a growing body of content and capability, rather than a one-off launch that becomes difficult to maintain.

I believe a website is best developed as an iterative plan for the content, activities, and needs of the years ahead. We can start with a clear foundation, learn from real use, and expand deliberately.

A three-year direction, built in practical stages

Year 1 — Foundation and core publishing: establish the digital home and content structure, train the people who will work on it, and put core publishing and enquiry workflows in place.

Year 2 — Federation and process integration: connect appropriate network capabilities, improve the path from enquiry to project, and strengthen team review and backup practices.

Year 3 — Operational maturity: extend workflows and integrations in response to demonstrated needs, improve reporting and partner connections, and build internal confidence to maintain the ecosystem.

This is a direction, not a rigid schedule. Priorities should follow your mission, resources, risks, and the evidence gathered as the system is used.

What this approach makes possible

• For organisational leaders: a coherent digital direction, ownership of key assets, and a practical basis for planning future capabilities.
• For staff: tools and training that support participation, review, and ongoing development.
• For end users: clear, responsive experiences designed to respect privacy and avoid unnecessary friction.
• For ecosystem partners: ways to discover one another, share selected public information, and collaborate without surrendering local autonomy.

Above all, Prometheus gives you a technical partner who can work across strategy and implementation. I bring the experience to understand complex requirements, the discipline to build maintainable systems, and the commitment to explain the work so your team can grow with it.

Let us explore what you need

If you are planning a new digital home, improving an existing one, connecting services, or building a longer-term technology roadmap, I invite you to start a conversation.

I will work with you to understand the mission, identify the real requirements, and determine how AmadeusWeb Spring, custom development, integrations, and team training can meet them.

Imran Ali Namazi
Founder, AmadeusWeb | Lead Technologist, Prometheus
imran@amadeusweb.in
+91-9566166880
AmadeusWeb | Prometheus